1. Wael Ellithy, Ph.D. Arx ICT 2009-07-08
Agile Software Development with Scrum The First Summer Workshop On Software Standards
Wael Ellithy, Ph.D.
Arx ICT

2. OUTLINE Agile Software Development Scrum Framework
Scrum Rules and Process
Scrum In Industry
Scrum : Implementation framework based on Agile development.

3. Agile software development
Iterative and adaptive development.
Cope with changing requirements.
No long-term planning.
Agile “timeboxes” activities into 1- 4 week cycles.
Customers/clients involved in the process.
A group of software development methodologies based on iterative development.
Agile is designed to cope with changing requirements. It is efficient because it builds quality into it’s processes.
Agile methods break tasks into small increments with minimal planning, and don't directly involve long-term planning.
Each iteration is worked on by a team through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders.

4. Agile software development (cont.)
Cross-functional and self-organizing teams.
Team size is typically small.
Daily meetings to discuss progress/problems.
Most agile teams work in a single open office.

5. Scrum Framework Iterative incremental framework
Used with agile software development.
Scrum is not an acronym.
Wrapper for existing engineering practices.
Scrum is an iterative incremental framework for managing complex work commonly used with agile software development.
Framework for non-predictable complex projects.
Scrum is a team-based approach to iteratively, incrementally develop systems and products when requirements are rapidly changing

6. How does Scrum work? Small teams (< 10 people)
A series of Sprints (1 - 4 weeks)
Visible, usable increments
Time-boxed scheduling

7. What Happens During a Sprint?
Frequent, daily short Scrum meetings.
Each team produces a visible, usable increment.
Each increment builds on prior increments.
Clearly defined deliverables and responsibilities.
Each team member buys into the assignment.

8. Scrum Rules
Scrum Master : who maintains the processes – Project Manager.
Product Owner: who represents the stakeholders.
Team: a cross-functional group of people who do the actual analysis, design, implementation, testing).
Scrum is a "process skeleton," which contains sets of practices and predefined roles.
The main roles in Scrum are:
Scrum Master (who maintains the processes – Project Manager).
Product Owner (who represents the stakeholders).
Team (a cross-functional group of people who do the actual analysis, design, implementation, testing).

9. What’s a Scrum Meeting?
Short ( min) frequent meetings, facilitated by the Scrum Master.
All team members attend—even teleworkers
One activity – Scrum Master asks each attendee 3 questions

10. What Are The 3 Questions?
1. What have you completed since the last Scrum meeting?
2. What got in your way of completing this work?
3. What will you do between now and the next Scrum meeting?

11. Scrum process flow
Product Backlog: Contains all product requirements and functions made by product owner, then prioritize this requirements.
Sprint backlog is filled by the scrum team

12. At the End of a Sprint Status meeting with all stakeholders.
Increments are delivered.
Surprises are reported.
New estimates and team assignments are made for the next Sprint.
The project can be cancelled.

13. Scrum in Industry Arx ICT company as a case study. Team size: 5 people
Sprints of 2 weeks
Daily Scrum meetings (~15 minutes)
Sprint planning (~ 2 hours)
Rally: agile project management tool

14. Scrum (Pros.) Productivity increases Series of manageable chunks
Everything is visible to everyone
Team communication improves
Customers obtain frequent feedback on how the product actually works
The product becomes a series of manageable chunks

15. Scrum (Cons.) Scrum meetings overhead (many meetings).
Interruptions from previous sprints(e.g. bugs).
Mission critical systems.
Not everybody likes that way of working.
People are resistant to change.

16. References http://en.wikipedia.org/wiki/Agile_software_development
spx

17. Thank you