Agile Sponsors
Featured Whitepapers
- Learn Ways to Keep Schedules and Costs in Line With Requirements Change Management
- Java Deployments in an Enterprise Environment
- Challenges & Characteristics of Enterprise Continuous Integration
- Build Release Plans That Deliver Customer Value!
- Improving Traceability and Auditability Across the Development Lifecycle
Upcoming and Recent WebCasts
How to implement Scrum in 10 easy steps - Step #9: Finish when you said you would |
 |
| Tuesday, 20 November 2007 06: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: 2571 Comments (0)
|
Show/hide comment form
| < Prev | Next > |
|---|
Agile Marketplace - Announcements and Special Offers
Webcast: Moving Build and Code Quality Upstream
This interactive panel discussion moderated by Bob Aiello, Editor-in-Chief fo the CM Journal brings industry experts Anders Wallgren, CTO of Electric Cloud and Gwyn Fisher, CTO of Klocwork together for a candid discussion of the cost savings, productivity and quality benefits that can be achieved by stabilizing builds and code quality as early in the development cycle as possible.
Register Now!
Collabnet -TeamForge 5.3
CollabNet TeamForge 5.3 includes Dynamic Planning—providing flexibility to model release scope and timeline in a single view. Now, you can easily manipulate/adjust release data.
Download Your Free Trial
Requirements-based testing (RBT) can help to ensure comprehensive test coverage, reducing the risk of failure and improving software quality. This white paper details how application lifecycle management can be used to more effectively implement RBT processes, offering greater collaboration, traceability and control.can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage.
Download the Requirements-Based Testing whitepaper
PureCM –SCM for Agile Teams
PureCM helps you to manage development in short iterations: keeping track of changes, supporting automated builds and preserving frequent snapshots of your projects.
Get the free trial now