gwc agile and scrum
TRANSCRIPT
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
Auth
ors
Split into teams Go!
We will build paper airplanes
Iterations and re-planning of 2 min each
Line production conceptThe plane starts in an edge and ends in the otherThe engineering of production is a team decisionTeams 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)
Basi
c ru
les
21
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
begi
nnin
g
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 windowsMust have a fly cabinMust have the logotype of your company on
both wingsMust fly across table (~2 meters)
The prototype will be shown to the group.
Start!Prop
osal
an
alys
is
The winner :Deliver more airplanesDeliver 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.
Prep
arat
ions
Client (me)Gives the scope and approves each
produced airplane
Team leaderThe 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.
TeamProduce the airplanes and check/act the
process.
Select a Team leader!
Role
s
Act/check time (2 minutes): Number of planned to finish planesAgree/improve work process
Start!
Work time (2 minutes): Number of planned to make planesProduce the planes
Start!
Show timeCount planes (done)
RepeatIter
atio
ns
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?Re
tros
pect
ive
s
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!
Cong
ratu
lati
ons!
5 principles1. Deliver every sprint2. Team decides everything3. Inspect and adapt everyday4. Define chief impediments
removal5. Priorities come from one
person
Scrum master1. Enforces the Scrum rules2. Facilitates all Scrum meetings3. Shields the team from external
interference4. Leads the team to be self-organized and
to continuously improve5. Coaches and supports PO6. Removes impediments
Responsible for the success of Scrum
Product owner1. Envisions the product2. Is the only one responsible for Product
backlog3. Is responsible for the product’s
profitability4. Decides on release date and content5. Accepts or rejects work results6. Collaborates with both the team and
stakeholders
Responsible for the product success
Team1. Self-organizing2. Cross-functional with no roles3. 7± 2 members4. Responsible for meeting their
commitments5. Authority to do whatever is needed to
meet commitments
Responsible for delivering product
4 meetings1. Sprint planning2. Daily scrum3. Sprint review4. Sprint Retrospectives5. Backlog grooming
Sprint planning1. PO presents top priority Product Backlog
items2. Team selects the amount of Backlog for the
upcoming Sprint3. Acceptance criteria are negotiated and
clarified4. Sprint Goal is defined
Define “what” to do
Sprint planning
1. Team participates while PO’s available2. Team breaks items into tasks to form
the Sprint Backlog3. Involves detailed design4. Team makes commitment for the
Sprint
Define “how” to do
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
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
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
Scru
mCustomers
Product Backlog
Team’s commitment
PlanningSprint Backlog
Backlog grooming
0 Changes
Sprint2
weeks Review
Stand-up
Feature release
Scrum Master
TeamProduct Owner
Retro
Final project & Scrum
1. All of you will form one Scrum team2. Elect Scrum Master and Product Owner3. Create your Product Backlog4. Decide on Sprints
Thank you!www.bebetterdeveloper.com
www.bebetterleader.com