Agile (SCRUM) Software Development Methodology

Scrum Practices (Key Process Item):
* Product Backlog
- Identified list of stories (Business Requirement) for that product

* Sprint Backlog
- Identified list of stories for that specific Iteration (Sprint) from the product backlog

* Daily Scrum
- Daily project standup meeting (max of 20 min)

* Sprint
- iteration which contain few identified stories and duration typically from 2-4 weeks

* Potentially Shippable product Increment

FrameWork:
* Roles
* Product Owner
* Scrum Master
* Scrum Team

* Ceremonies
* Sprint Planning
* Sprint demo/review
* Sprint retrospective
* Daily Scrum

* Artifacts
* Product backlog
* Sprint backlog
* Burndown charts

Common challenges addressed by Agile/Scrum:
* Not sustainable ? - Sustainable pace
* Not scalable ? - Cross-functional teams
* Don't deliver highest value for customers ? - Ranked backlogs
* Work-in-progress = waste ? - Potentially shippable product increments
* Group demoralized by delivering software that's not used ? - Customer part of team
* Quality suffers? - Short, frequent feedback loops: Inspect and Adapt
* Real problems obscured ? - Pull quality forward
* Risk increase because failure occurs late ? - Burning visibility
* Walls prevent good communication ? - Welcome change
* First phase often overloaded ? - Disciplined processes harness opportunities for change
* Later phases sometimes dropped? - Empirical approach

About Author / Additional Info:
Arivuvel Ramu
Technical Architect (SOA)
GalaxyESolutions