|
|
|
| About Agile |
| |
Why Scrum?
Capable embraces the Agile Scrum approach to software specification, development and testing.
Scrum embodies lean principles which maximize customer value while minimizing waste, creating more with less.
Scrum teams deliver functioning code as negotiated with a client (the Product Owner) in frequent, short bursts of activity called Sprints.
|
Scrum delivers the right results, right away
- Clients (product owners) get what they want, quickly, in priority order
- Scrum is simple, transparent, immediate and broadly applicable
- Up-front investment in requirements is relatively small; only the highest-priority user stories get attention and refinement before each Sprint
- Transparency exposes risks and issues quickly; addressing these as they come up keeps costs down
- Short iterations and close work with product owners provides many opportunities for teams to become cohesive, high-performing, and successful
|
Scrum is simple: Here's a four-sentence summary
- Product owners create a “product backlog” of requirements and/or business process improvement goals from Value Stream Mapping
- Product owners work with team members to refine goals and requirements into user stories using the INVEST model: each user story should be Independent, Negotiable, Valuable, Estimable, Small and Testable.
- Product owners prioritize user stories, then work with agile teams to define the scope of deliverables to be developed in short iterations (Sprints)
- Agile teams develop and test the desired functionality, then demonstrate completed user stories to the Product Owner during the Sprint Review
|
Agile scrum teams develop high quality, robust code with each iteration
- Teams members effectively conduct continuous peer review of design, code and test artifacts
- Continuous integration results in code that is always verified against the existing base
- Test automation, and regular application of regression tests, quickly detects unexpected side effects
|
Scrum works well with existing infrastructure
- Legacy estimation and forecasting processes can be adapted to work with Agile artifacts
- Legacy software release process and support infrastructure can be utilized with Agile development
|
Scrum Has Just Three Roles
- Product Owner: responsible for the business value of the project
- Scrum Master: ensures that the team is functional and productive
- Team Member: Team members self-organize to get the work done. Team Members typically include Analysts, Developers and Testers.
Everyone is expected to help achieve the common goal using whatever skills they have or can develop, provided coding and other applicable industry standards are respected. Enterprise architects, DBAs, and other infrastructure resources are consulted as needed.
|
Scrum Has Just Four Ceremonies
- Sprint Planning: the team meets with the product owner to choose a set of work to deliver during a sprint
- Daily Scrum: the team meets each day to share struggles and progress
- Sprint Review: the team demonstrates to the product owner what it has completed during the sprint
- Sprint Retrospective: the team looks for ways to improve the product and the process.
|
Scrum Has Just Three (Official) Artifacts
- Product Backlog: ordered list of ideas for the product
- Sprint Backlog: set of work from the product backlog that the team agrees to complete in a sprint, broken into tasks
- Product Increment: required result of every sprint. It is an integrated version of the product, kept at high enough quality to be shippable
|
Scrum is Simple But Not Easy to Implement
|
Recommended Agile Toolsets
|
|
|
|
|
