8 Questions to Answer Before You Begin

17:17 GMT  |  Read comments(0)

Meet the Antipreneurs

They profit from the free market, but they criticize it, too. So how do they get away with it?

http://www.businessweek.com/magazine/content/08_66/s0806032873701.htm?chan=magazine+channel_bwsmallbiz+--+top+stories

17:03 GMT  |  Read comments(0)

24 June

Iteration Length?

Our organisation has always used two week iterations and sometimes we do wonder if two weeks is optimum, Well the first thought was for enhancement projects two weeks fits the bill, these could be projects where the solution to implement the features is available to the team, but for a brand new project which includes a technical learning curve and innovation, three weeks might be be apt. This is subject to discussion with the teams. Although Scum recommends a 30 day iteration, 2 week iterations yield results and 3 week iterations will yield innovative results. At the end of the day both iteration lengths are within the realm of Scrum and it is a variable available to teams and the product owner, how it is varied or used as long as the goals of the release are met, is not important.

Based on previous experience with two week iterations I have made some observations which kind of remind us the strength of the two week iteration

• Two weeks is just about enough time to get some amount of meaningful development done.
• Two week iterations indicate and provide more opportunities to succeed or fail.e.g, within a 90 day release plan, 5 - 2-week iterations of development and 1 stabilisation iteration at the end make it possible to have checkpoints on the way to the release.
• The 2-week rhythm is a natural calendar cycle that is easy for all participants to remember and lines up well with typical 1- or 2-week vacation cycles, simplifying capacity estimates for the team.
• Velocity can be measured and scope can be adjusted more quickly.
• The overhead in planning and closing an iteration is proportioned to the amount of work that can be accomplished in a two week sprint.
• A two week iteration allows the team to break down work into small chunks where the define/build/test cycle is concurrent. With longer iterations, there is a tendency for teams to build a more waterfall-like process.
• Margin of error for capacity planned and available is lesser in two week iterations.

Well the above is on the basis of what I have observed and may be different in your organisation.

16:09 GMT  |  Read comments(0)

Iteration Length?

Our organisation has always used two week iterations and sometimes we do wonder if two weeks is optimum, Well the first thought was for enhancement projects two weeks fits the bill, these could be projects where the solution to implement the features is available to the team, but for a brand new project which includes a technical learning curve and innovation, three weeks might be be apt. This is subject to discussion with the teams. Although Scum recommends a 30 day iteration, 2 week iterations yield results and 3 week iterations will yield innovative results. At the end of the day both iteration lengths are within the realm of Scrum and it is a variable available to teams and the product owner, how it is varied or used as long as the goals of the release are met, is not important.

Based on previous experience with two week iterations I have made some observations which kind of remind us the strength of the two week iteration

• Two weeks is just about enough time to get some amount of meaningful development done.
• Two week iterations indicate and provide more opportunities to succeed or fail.e.g, within a 90 day release plan, 5 - 2-week iterations of development and 1 stabilisation iteration at the end make it possible to have checkpoints on the way to the release.
• The 2-week rhythm is a natural calendar cycle that is easy for all participants to remember and lines up well with typical 1- or 2-week vacation cycles, simplifying capacity estimates for the team.
• Velocity can be measured and scope can be adjusted more quickly.
• The overhead in planning and closing an iteration is proportioned to the amount of work that can be accomplished in a two week sprint.
• A two week iteration allows the team to break down work into small chunks where the define/build/test cycle is concurrent. With longer iterations, there is a tendency for teams to build a more waterfall-like process.
• Margin of error for capacity planned and available is lesser in two week iterations.

Well the above is on the basis of what I have observed, it is not

16:08 GMT  |  Read comments(0)

23 June

Five Levels of Planning in Scrum

In agile methods, a team gets work through iteration planning. Due to the shortness of the iteration a planning gains importance than an actual plan. The disadvantage of iteration planning when applied to projects that run for more then a few iterations or with multiple teams is that view of long term implications of iteration activities can be lost. In other words: the view of ‘the project as a whole’ is lost.

Planning activities for large-scale development efforts should rely on five levels

• Product Vision
• Product Roadmap
• Release Plan
• Sprint Plan
• Daily Commitment

Each of the five levels of planning help us address fundamental planning principles of priorities, estimates and commitments.

18:18 GMT  |  Read comments(0)