7. SCRUM Master for a day
Intro to the ‘Daily Story’
Check current status
Choose an actionable item
Use the Fact/Expectation/Correction technique to
share with team
7
Supervision 101
Looking for good intent
Levels of Feedback: Identity, Values, Abilities,
Behavior
7
QUALITY. PRODUCTIVITY. INNOVATION.
11. The SCRUM Board – January 2013
11
11
QUALITY. PRODUCTIVITY. INNOVATION.
12. The SCRUM Board – February 2013
12
12
QUALITY. PRODUCTIVITY. INNOVATION.
13. The SCRUM Board – July 2013
13
13
QUALITY. PRODUCTIVITY. INNOVATION.
14. The SCRUM Board – October 2013
14
14
QUALITY. PRODUCTIVITY. INNOVATION.
15. The Board is not enough
QUALITY. PRODUCTIVITY. INNOVATION.
16. The Retrospectives
Two things are fundamental in SCRUM:
Ship running, tested software every Sprint. (DONE == DONE)
16
Reflect frequently on how it’s going, and revise your practices
in accord with what you observe. (Inspect and Adapt)
Source: http://xprogramming.com/blog/what-is-really-essential/
16
QUALITY. PRODUCTIVITY. INNOVATION.
17. Quality is Not Negotiable (I)
Architecture Diagram
Technical Solution to Architect Early
17
Demo Preview to PO
Task Teams: 1Dev + 1Test
Mid sprint checkpoint
17
QUALITY. PRODUCTIVITY. INNOVATION.
18. Quality is Not Negotiable (II)
Knowledge Transfer
Team code review, Holiday KT, Share Solutions
Owner per component
How2DEMO
Technical debt assessment
Bugs Analysis and Grouping
RFT (Ready For Test)
18
18
Revision:
fc876cd005902515508e9a4f0709f852dd0ae09c
Author: Dragos Dobromir
<dragos.dobromir@endava.com>
Date: 18/10/2013 17:58:09
Message: RFT_v1.0_EventAdapter_PEP-2135 Update EventAdapter WSDL+BPEL with OES
QueryClearPAN operation
QUALITY. PRODUCTIVITY. INNOVATION.
19. JIRA - One unified source of information
• All decision taken as a result of
conversation, mail, phone to be visible to all
team members
19
• Dependencies – managed in jira (new
column dead line)
• Technical Impediments
19
QUALITY. PRODUCTIVITY. INNOVATION.
