As a team developing and evolving a product, defects are inevitable, whether they are discovered internally or reported by external customers. Back in the days of waterfall methodology, teams would meet at a regular cadence to review bugs and set priority and severity. Bug Triage meetings were typically driven by the QA team. As companies continue… Read More Agile Practices – Bugs
In agile, time spent performing in-depth investigation of a problem, evaluating technical design options, or doing a proof of concept to validate the effectiveness of a specific technology or technical design option is tracked as a ‘spike’. A spike is a research story representing effort needed for investigation of a problem or evaluation of one or… Read More Agile Practices – Spikes
According to the Agile Alliance, velocity is a measurement of the amount of estimated effort that a team can support in one sprint. Why is velocity important? As Product Managers, we often need to forecast how long it will take to complete a project, or a set of features, so that we can set expectations… Read More Agile Practices – What is Velocity?
Our team recently got together for a hackathon. I wanted to share both my experience being a part of that, and my thoughts around the impact the hackathon had on the team. First of all, the hackathon was planned as a 1-day event (during business hours). It was presented more as an optional event; namely,… Read More The Beauty of Hackathons
Often times, things come up during Daily Standup that require more elaborate discussion. Perhaps there is a bug that someone worked on, which leads to questions or involves a more in-depth explanation. Alternatively, there may be a design option or a controversial change under consideration, which provokes opinions across the team. Or maybe there are… Read More Agile Practices – Parking Lot
Observations From A Seattleite 