Upgrade to Pro — share decks privately, control downloads, hide ads and more …

GWC Agile and Scrum 101

GWC Agile and Scrum 101

Introduction to Agile development process. Basics of Scrum.

Lena Barinova

March 26, 2016
Tweet

More Decks by Lena Barinova

Other Decks in Technology

Transcript

  1. Flavio Steffens de Castro, author of www.agileway.com.br Rafael Prikladnicki, professor

    from PUCRS and agile coach and trainer www.inf.pucrs.br/~rafael Authors
  2. Split into teams Go! We will build paper airplanes Iterations

    and re-planning of 2 min each Line production concept The plane starts in an edge and ends in the other The engineering of production is a team decision Teams are not allow to stock sheets for production The product (airplanes) MUST conform with the scope defined If a product doesn‘t pass the final quality review, it will not be accepted in the iteration Products that are unfinished can be used in the next iteration to be complete Every team will represent a factory (with logo) Basic rules 2 1
  3. The Air Force is planning to buy some new airplanes

    The agent of the Air Force (me) contacted your factories to check for your proposals I want to know how many airplanes you can deliver in TWO minutes Since I am very impatient, you have ONE minute to discuss and inform the number of airplanes you produce in a TWO minute iteration Start! The beginning
  4. The Air Force liked the estimates and will open a

    competition You will have TWO minutes to produce a prototype. The scope is: Must have 12 windows Must have a fly cabin Must have the logotype of your company on both wings Must fly across table (~2 meters) The prototype will be shown to the group. Start! Proposal analysis
  5. The winner : Deliver more airplanes Deliver the quantity as

    promised 4 iterations of 2 minutes to produce the planes 2 minutes at the end of each iteration to check and act about your production line, to increase productivity. You will give the estimates in the beginning of each iteration. Preparations
  6. Client (me) Gives the scope and approves each produced airplane

    Team leader The leader can‘t build the airplanes. The leader should take care of the team, help to with the process, remove impediments and get the material. Team Produce the airplanes and check/act the process. Select a Team leader! Roles
  7. Act/check time (2 minutes): Number of planned to finish planes

    Agree/improve work process Start! Work time (2 minutes): Number of planned to make planes Produce the planes Start! Show time Count planes (done) Repeat Iterations
  8. Did you get what the client wanted in the beginning?

    Did the prototype help? Why? Did the estimates got better with time? Why? Was the concept of inspect/adapt useful? What was the most useful? Did team leader help? How? Who made decisions? What is better for you and the client: Deliver all the airplanes in 10 minutes? Deliver a % of airplanes each 2 minutes? Retrospectives
  9. You had just lived an Agile Process! The teams became

    motivated and self-managed The team leader worked for the team The work process became more efficient and organized in iterations The communication became strong and powerful You inspected and adapted, through iterations! Congratulations!
  10. 5 principles 1. Deliver every sprint 2. Team decides everything

    3. Inspect and adapt everyday 4. Define chief impediments removal 5. Priorities come from one person
  11. Scrum master 1. Enforces the Scrum rules 2. Facilitates all

    Scrum meetings 3. Shields the team from external interference 4. Leads the team to be self-organized and to continuously improve 5. Coaches and supports PO 6. Removes impediments Responsible for the success of Scrum
  12. Product owner 1. Envisions the product 2. Is the only

    one responsible for Product backlog 3. Is responsible for the product’s profitability 4. Decides on release date and content 5. Accepts or rejects work results 6. Collaborates with both the team and stakeholders Responsible for the product success
  13. Team 1. Self-organizing 2. Cross-functional with no roles 3. 7±

    2 members 4. Responsible for meeting their commitments 5. Authority to do whatever is needed to meet commitments Responsible for delivering product
  14. 4 meetings 1. Sprint planning 2. Daily scrum 3. Sprint

    review 4. Sprint Retrospectives 5. Backlog grooming
  15. Sprint planning 1. PO presents top priority Product Backlog items

    2. Team selects the amount of Backlog for the upcoming Sprint 3. Acceptance criteria are negotiated and clarified 4. Sprint Goal is defined Define “what” to do
  16. Sprint planning 1. Team participates while PO’s available 2. Team

    breaks items into tasks to form the Sprint Backlog 3. Involves detailed design 4. Team makes commitment for the Sprint Define “how” to do
  17. Daily scrum 1. What have you completed since last meeting?

    2. What will you complete before next meeting? 3. What is in your way? Inspection and adaption for the sprint
  18. Sprint review 1. Team presents the “Done” work and “Undone”

    work 2. Get feedback from the Product Owner and Stakeholders 3. Update Product Backlog and release Burndown chart Inspection and adaption for product
  19. Sprint retrospectives 1. Scrum Team inspects the last sprint regarding

    people, relationships, processes and tools 2. Scrum Team identifies possible improvements and agrees on the measures for next Sprint 3. Scrum Team may update its own working agreement Inspection and adaption about process
  20. Scrum Customers Product Backlog Team’s commitment Planning Sprint Backlog Backlog

    grooming 0 Changes Sprint 2 weeks Review Stand-up Feature release Scrum Master Team Product Owner Retro
  21. Final project & Scrum 1. All of you will form

    one Scrum team 2. Elect Scrum Master and Product Owner 3. Create your Product Backlog 4. Decide on Sprints