1 / 16

The SCRUM Sprint Cycle

The SCRUM Sprint Cycle. CSCI 216: Web/Database Capstone. What is a Sprint?. A 1-4 week cycle in which development work is done Ours will last one week Also called an “iteration” New functionality is delivered at the end of each sprint. Week. T he Product Backlog.

jiro
Download Presentation

The SCRUM Sprint Cycle

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. The SCRUM Sprint Cycle • CSCI 216: Web/Database Capstone

  2. What is a Sprint? • A 1-4 week cycle in which development work is done • Ours will last one week • Also called an “iteration” • New functionality is delivered at the end of each sprint

  3. Week

  4. The Product Backlog • Aprioritized features list • Contains short descriptions of the functionality desired in the product • You do NOT need document all requirements up front • A Scrum team and the product owner begin by writing down everything they can think of easily. • The product backlog is allowed to grow and change as more is learned about the product and its customers. • The product backlog should be reviewed after each Sprint Review. • Items may be added, deleted, or reprioritized. • The updated product backlog should signed by the client.

  5. The Product Backlog • A typical product backlog includes: • Features • Bugs • Technical work • Knowledge acquisition • Features on the backlog are expressed as user stories • Short, simple descriptions of the desired functionality told from perspective of the user. • Form: "As a(n) ___, I want to ___ so that ___." • Example: "As a shopper, I can review the items in my shopping cart before checking out so that I can see what I've already selected."

  6. Sample Product Backlog Product Backlog for Gail's Creative Crafts Team TBA:  Ryan Justice, Vinh Thai Nguyen and DeAnn Gaull As a Customer, I want to see key product features and a picture of the products on the home page so that I can get a quick idea of what is sold As a Customer, I want to be able to read about Gail and her business An an Owner, I want a secure site that will not get hacked An an Owner, I want my content backed up so that I will not lose anything As a Customer, I want to be able to click on an item to learn more about it. As a Customer, I want to be able to securely purchase an item online, and I want to be able to use my credit card. An an Owner, I want a logo that communicates by business to my and gives them a good feeling about my products An an Owner, I want to be able to add and update text about Fabric Care. As a Customer, I want to find events where the owner has a craft booth (events page) I can actually see (and touch) a wider selection of pillows and other products. An an Owner, I want to update patterns, pictures, and prices so that customers have the most current products and prices. As a Customer, I want be able to navigate the site easily. I can find the information I am looking for. As a Customer, I want to be able to search by pillow type or pattern to find what I’m looking for. Client Signature: ______________________________________________

  7. The Sprint Process • Sprint Planning Meeting • Sprint Development • Sprint Review

  8. Sprint prioritization Sprint planning Sprint goal Sprint backlog • Analyze and evaluate product backlog • Select sprint goal • Decide how to achieve sprint goal (design) • Create sprint backlog (tasks) from product backlog (user stories) • Decide who does what • Estimate sprint backlog in hours Sprint planning meeting

  9. Sample Sprint Backlog

  10. Sprint Development • Estimated work remaining is updated daily • Any team member can add, delete or change the sprint backlog • If work is unclear • Define a sprint backlog item with a larger amount of time and break it down later • Update work remaining as more becomes known • Log actual time in Redmine • Submit client meeting notes in Redmine • Update the live site

  11. The Sprint review • Describe the sprint goal(s), in the form of user stories • Demonstrate the new features • This is informal • No PPT needed! • Don't spend more than 10 minutes presenting (including time for feedback) • Elicit feedback

  12. After the Sprint Review • Complete a Retrospective • Update your Working Agreement, if needed • Update your Definition of Done, if needed • Revise your Product Backlog, and turn in a printed copy • Indicate completed items • Get your client's signature or an email approving changes • Create a Sprint Backlog for the upcoming week, and turn in a printed copy • Enter new sprint tasks in Redmine

  13. The Working Agreement • Becoming an effective team requires a commitment to working together and supporting one another toward common goals and objectives. • Working agreements help team members identify and share their values, and address potential concerns and issues up front. • The Working Agreement may address issues including items such as: • meetings (how often? when? where? how long?) • coding standards and conventions • code reviews and testing • pair programming • delegation of responsibility (e.g. who updates the Product Backlog)

  14. The Working Agreement • All team members contribute to the Working Agreement • Each team member should have an opportunity to share what they feel will enable the team to effectively work together.   

  15. A Working Agreement is public. • It will be signed by each team member and posted on the wall. • A Working Agreement is dynamic. • It should be updated periodically. • A Working Agreement is unique. • Each agreement should be tailored to the specific needs of the team. • A Working Agreement is informal.

  16. The Definition of Done • When is a sprint "Done"? • A team's Definition of Done is an agreed-upon set of things that must be true before any product backlog item is considered complete. • Think of the definition of done as a special set of conditions of satisfaction that are added to every user story (product backlog item). • For the user story to be done, not only must all of the conditions of satisfaction be fulfilled but so must the items that make up the definition of done.

More Related