Posts Tagged: sprint planning

Forget about poker planning

Explaining agile estimating and planning is the hardest part when teaching a class. That’s because people freak out when they hear about story points and relative estimations. Why wouldn’t they? If you’ve ever done a project before in your life,

Forget about poker planning

Explaining agile estimating and planning is the hardest part when teaching a class. That’s because people freak out when they hear about story points and relative estimations. Why wouldn’t they? If you’ve ever done a project before in your life,

Variation in software estimation

Last week I visited Warsaw, Poland for the first edition of Agile By Example. The organization did a great job setting up this conference.  For instance, they opened a call for solutions on their website, where people could list the

Variation in software estimation

Last week I visited Warsaw, Poland for the first edition of Agile By Example. The organization did a great job setting up this conference.  For instance, they opened a call for solutions on their website, where people could list the

Healthy flow with classes of service

Last week I attended Lean & Kanban Europe 2010.  It was the first conference I attended with such a specific focus on lean software development. My expectations were largely fulfilled thanks to some great sessions and thought provoking ideas. Being

Healthy flow with classes of service

Last week I attended Lean & Kanban Europe 2010.  It was the first conference I attended with such a specific focus on lean software development. My expectations were largely fulfilled thanks to some great sessions and thought provoking ideas. Being

Holiday velocity

An agile team is known by its capability to plan as a team. The team commits to a certain amount of features to be realized within a certain amount of time. They often use historical data to determine how much

Holiday velocity

An agile team is known by its capability to plan as a team. The team commits to a certain amount of features to be realized within a certain amount of time. They often use historical data to determine how much

Small user stories generate flow

Creating user stories feels like common practice and is often experienced as ‘just a tool to communicate requirements’, but they can have a serious impact on the delivery of a team. I’ve watched different product owners in different projects pouring requirements

Small user stories generate flow

Creating user stories feels like common practice and is often experienced as ‘just a tool to communicate requirements’, but they can have a serious impact on the delivery of a team. I’ve watched different product owners in different projects pouring requirements

No more time based estimates

We recently switched from a mix of velocity and timebased estimations to pure velocity based planning. How did we work in the past? The product owner selects a number of user stories, which are sorted by priority. She uses the

No more time based estimates

We recently switched from a mix of velocity and timebased estimations to pure velocity based planning. How did we work in the past? The product owner selects a number of user stories, which are sorted by priority. She uses the