1 / 27

SCRUM basics

SCRUM basics. Julie Rudder & Claire Stewart. Outline. What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie) How to decompose to tasks (Julie) Rules! team pulls work, etc. (Julie). What is Scrum?.

cadee
Download Presentation

SCRUM basics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCRUM basics Julie Rudder & Claire Stewart

  2. Outline What is scrum (Claire) Scrum roles (Claire) Scrum rhythms and processes (Claire) How to write stories (Julie) How to decompose to tasks (Julie) Rules! team pulls work, etc. (Julie)

  3. What is Scrum? • Agile project management methodology • Focus on reducing complexity by breaking down work • Short work cycles with frequent deliverables, iteration • Emphasis on making work visible

  4. Scrum roles The person responsible for maintaining the Product Backlog by representing the interests of the stakeholders. Drives work by writing stories, and decides when they are done. Available to the team. Product Owner The person responsible for ensuring the Scrum process is used properly and facilitating resolution of issues raised by the Scrum Team. Does not direct the Team, but facilitates their work. Scrum Master Team A cross-functional group of people responsible for managing itself to develop the product. Breaks down Stories into Tasks & executes them. Stakeholders The people for whom projects are completed. They are directly involved only during sprint reviews.

  5. Source:http://www.mountaingoatsoftware.com/scrum-figures

  6. Traditional components of Scrum

  7. The Board

  8. Story Format As a: I want to: So that: Done looks like:

  9. Story Format As a: < from the user perspective > I want to: So that: Done looks like:

  10. Story Format As a: < from the user perspective > I want to: < in narrative form, briefly explain the feature> So that: Done looks like:

  11. Story Format As a: < from the user perspective > I want to: < in narrative form, briefly explain the feature> So that: < why is this feature important? > Done looks like:

  12. Story Format As a: < from the user perspective > I want to: < in narrative form, briefly explain the feature> So that: < why is this feature important? > Done looks like: < what is the acceptance criteria? >

  13. How to write stories: Good stories Stories are told from the perspective of the user. Stories are understood by the team and can be broken into discrete tasks. Stories contain work that are to be done by the team. Stories are ready to be started. Stories have acceptance/done criteria.

  14. Bad story - too big

  15. Bad example - too big

  16. Better story As a: System Administrator I want to: easily integrate my campus authentication system with Curate. So that: users at my institution can log in with their campus credentials. Done looks like: Curate has a flexible authentication system that allows new institutions to configure their campus preferred authentication system without writing new code. Common systems are CAS, LDAP, SHIBBOLETH, and more.

  17. Sizing Stories Assign a value to each story to measure COMPLEXITY and SIZE of the story relative to you team. Sizing helps us: • locate unknowns in the work and add needed information • build team consensus of the work to be done

  18. How to size 2 = very fast and easy to do in small amount of time and effort 4 8 16 32 = too big, too unknown - needs to be broken down into smaller stories

  19. Most stories should be around 2 = very fast and easy to do in small amount of time and effort 4 8 16 32 = Too big, too unknown - needs to be broken down into smaller stories

  20. If sizing is all over the place

  21. If sizing is all over the place Team members explain why they assigned certain numbers.

  22. If sizing is all over the place Team members explain why they assigned certain numbers. Team comes to consensus about the size.

  23. Decompose stories to tasks Tasking is not a way of accounting for time spent but a way to keep atomic chunks of work in front of people's eyes, so that the team can see at a glance what is available to do and what may be blocked.

  24. Rules! Team driven work Pull your own work (tasks) Standups exist for the team - team members should address the team without worry of being too technical, it’s not a report to POs All team members required to attend stand up (of course you will be out sometimes) Show up on time, end on time Make your work visible

  25. Discussion, questions It can take a little while to get used to Scrum! What questions do you have?

More Related