Agile UP
- Agile (foaled 1902 in Kentucky) was an American Thoroughbred racehorse that was the winner of the 1905 Kentucky Derby
- UP was not meant by its creators to be heavy or un-agile, it was meant to be adopted and applied in the spirit of adaptability and lightness—an agile UP
- Prefer a small set of UP activities and artifacts
- Since the UP is iterative and evolutionary, requirements and designs are not completed before implementation. They adaptively emerge through a series of iterations, based on feedback.
- Apply the UML with agile modeling practices
- There isn’t a detailed plan for the entire project. There is a high-level plan (called the Phase Plan) that estimates the project end date and other major milestones
Other Critical UP Practices
Some additional best practices and key concepts in the UP:
- Tackle high-risk and high-value issues in early iterations
- Continuously engage users for evaluation, feedback, and requirements
- Build a cohesive, core architecture in early iterations
- Continuously verify quality; test early, often, and realistically
- Apply use cases where appropriate
- Do some visual modeling (with the UML)
- Carefully manage requirements
- Practice change request and configuration management
No comments:
Post a Comment