How to implement Scrum in 10 easy steps - Step #9: Finish when you said you would |
 |
| Tuesday, 20 November 2007 07:21 |
 So you?ve got your backlog in order, ...
So you?ve got your backlog in order, estimated your backlog, clarified your requirements, planned your sprint and created a collaborative workspace.You're sprinting to achieve your sprint goals, running daily stand-up meetings and you're tracking progress with a daily burndown chart. Now you just need to finish when you said you would... What a great idea! What an insight! If only I'd thought of that, my development projects would never have been so hard :-) Seriously though, there are a few key principles of agile software development that help with this step. Here they are... 'done' means DONE! *Complete* each feature before moving on to the next. In agile development, 'done' means DONE!. All too often in software development, software is not in a shippable state. Having all the features 80% complete is of no use to anyone. However, 80% of features 100% complete might well be a perfectly shippable product. Hang on to this principle. Time waits for no man! Particularly on BAU (Business As Usual) product developments, you are usually in complete control of how many features, enhancements and bug fixes are in each release. If you hang on to the 'done' principle, you should be in a position to ship when your time is up. All changes must be reversible One of the key challenges in achieving this, is to ensure your software is always in a shippable state, even when you have multiple streams of development (e.g. live bug fixes alongside major project) on the go at the same time. To achieve this, all changes must be reversible. Finish when you said you would That's it. *Complete* each feature before moving on to the next. Stick to the principle 'done means DONE!'. Manage your code carefully so you can build a shippable product at any time. And even if it means varying the scope (that's varying scope, not varying quality), finish when you said you would. Follow this series by email
See also: 10 Key Principles of Agile Software Development How to implement Scrum in 10 easy steps: - Step #1: Get your backlog in order! - Step #2: How to estimate your product backlog - Step #3: Sprint Planning/clarify requirements - Step #4: Sprint Planning/estimate tasks - Step #5: Create a collaborative workspace - Step #6: Sprint! - Step #7: Stand up and be counted! - Step #8: Track progress with a daily burndown chart Read the full Story >>
Set as favorite
Bookmark
Email this
Hits: 3213 Trackback(0)Comments (0)
|
TrackBack URI for this entry
Show/hide comment form
Agile Marketplace - Announcements and Special Offers
Upcoming Webcasts
Sponsored by Urbancode - On Demand
Mastering Complex Application Deployment
Sponsored by CollabNet - Wednesday, August 24, 2011
Closing the Agile Loop: Continuous Integration, Continuous Information
ScrumWorks Pro – The World’s Best Agile Project Management Tool
Simply put, CollabNet’s ScrumWorks Pro is the best Agile project management solution on the market, bar none. More than 150,000 Agile professionals rely on the power and simplicity of ScrumWorks every day. But don’t take our word for it – try it yourself for free. CollabNet is now providing the first 10 users of ScrumWorks Pro at no charge!
Download ScrumWorks Pro today!
The Business Case for ALM Transformation
Are legacy systems holding your company back? Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper