Introduction to Scrum

There used to be only one way to build and manage IT systems. Plan the system from start to finish and then build it. Nowadays things are different. Systems are more complex than ever and change happens daily. Agile methodologies have grown out of this new IT world and they're not going away. So how can an agile methodology like Scrum help your efforts and how does it work anyway? This session will introduce the Scrum process and show how it could work in your organization.

Transcript

1. Richie Rump @Jorriss www.jorriss.net
3. • It’s a framework to get things done. • Designed for complex projects. • Iterative process. • Shippable software, frequently. • Handles frequent changes.
4. • Embrace Change • Frequent Delivery of Software • Better Risk Management • Greater Team Involvement • Better Software Quality
5. Source: http://www.mountaingoatsoftware.com/blog/agile-succeeds-three- times-more-often-than-waterfall
6. • Individuals and interactions over processes and tools • Completed functionality over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan
7. • Product Owner • Dev Team • Scrum Master
8. • Sprint Planning • Daily Scrum (Standup) • Sprint Review • Sprint Retrospective
9. • Product Backlog • Sprint Backlog • Burndown Chart
10. • One person • Accountable for product • Owns Product Backlog • Responsible for ordering items in Product Backlog • Responsible for clearly expressing Product Backlog items.
11. • Professionals that “Do the work”. • Self-organizing – Selects what to work and choses how to do it. • Cross-functional – the team has all of the skills necessary to deliver an increment. • Do not contain sub-teams. • Accountability is shared
12. • Ensures Scrum is understood and enacted. • Facilitates events as needed. • Removes impediments and blockers. • Servant leader. • Serves the Product Owner, Dev Team and the Organization.
13. • Less than 30 days • Most are two weeks long • Has a goal • No changes are made that would affect the goal • Scope may be clarified during the Sprint
15. • What will be done this Sprint? • How will the chosen work get done? • Creates a Sprint Backlog and a Sprint Goal. • Forecast the work for the Sprint. • At the end we will have created shippable software. • Define “done”.
17. • Fifteen minute meeting • Held every day • What has been accomplished since the last meeting? • What will be done before the next meeting? • What obstacles are in the way? • Inspect and adapt the Sprint Backlog
19. • Time boxed; one hour per week of sprint. • Involves the Scrum Team and stakeholders. • Demos the work done. • Records feedback and places in Product Backlog
20. • Scrum team only; no outsiders. • Inspect how the sprint went with regards to people, process and tools. • Creates a plan for implementing improvements.
21. Photo credit: http://sambit-daspatnaik.blogspot.com/2012/03/importance-of-project-management.html
22. • Scrum Guide : http://www.scrum.org/Scrum-Guides • Scrum Primer: http://scrumfoundation.com/library • Scrum Fundamentals on PluralSight.
23. Richie Rump @Jorriss http://jorriss.net http://slideshare.net/jorriss http://dotnetmiami.com