Do I have a role?    Michael “Doc” Norton        @DocOnDev    http://leandog.com     doc@leandog.com
Yes!
Yes! NO!Well...
Yes, but...Agile is aboutwhole team
Individuals and                        Working Software  Interactions         Over                      Over  Processes an...
Build projects around motivated      The best architectures,         individuals. Give them therequirements, and designs e...
So let’s meet the team
TheTeam
I am Laura,the Project  Manager
I am Brad, theLead Developer
I am Rachel, the    QA Lead
I am Paul, theBusiness Analyst
TheTeam
Requirements   Working Code
Let’s talkabout roles onan agile team
Servant Leadership
Servant Leadership✦   Facilitate✦   Remove Roadblocks✦   Protect the Team✦   Team Manages Process
But...... I don’t think this team is ready to           manage themselves
Lightweight Requirements
Lightweight Requirements    ✦   Index Cards    ✦   Story Mapping    ✦   Progressive Elaboration    ✦   In Order To, As A, ...
But...... we’ll build the wrong thing
Executable Tests
Executable Tests✦   Write Tests First✦   Test Continuously✦   Automated Testing✦   Communicate & Collaborate
But...... we don’t have time to build tests
Collective Ownership
Collective Ownership ✦   Program in Pairs ✦   Test / Code / Refactor ✦   Continuous Integration ✦   Communicate & Collabor...
But...... you’ll slow me down
Let’s               eliminate the                   silosRequirements            Working Code
You can work together onrequirements
You can work together on automation
This won’t be easy.
But it’ll be worth it.
Tuckman’s Stagesof Group Development
Forming
Storming
Norming
Performing
We discuss  stories in a“three amigos”    meeting
We Inspect and    Adapt
And...... the team makes good decisions        while I help shepherd
And...... we build what we need as we go
And...... now everyone is involved in            testing
And...... the whole team delivers in short                cycles
Everyone has a roleWe are all team members      Michael “Doc” Norton          @DocOnDev      http://leandog.com       doc@...
Do I have a role?
Do I have a role?
Do I have a role?
Do I have a role?
Do I have a role?
Do I have a role?
Do I have a role?
Upcoming SlideShare
Loading in...5
×

Do I have a role?

938

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
938
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Been with the company for over 10 years\nConsidered an excellent Project Manager\nSuccess due to her ability to manage all aspects of a project and keep team focused\nProperly submits all TPS reports\n\n
  • \n
  • Started here 2 years ago\nCoder hero / Rockstar\nWorks long hours, alone.\nOften seen wearing headphones\n
  • \n
  • Been with company 7 years\nStarted in Sales/Marketing; Moved to QA for Web Projects\nFrustrated she never gets enough time to test\nAttends conferences and is studying automated testing in her own time\n
  • \n
  • MBA with the company 4 years\nConvinced he should have Laura’s Job by now\nMeticulous about document formatting\nWishes they’d hurry up an invent a tool that writes code based on good specs\n
  • \n
  • Laura is conduit for all information\nPaul communicates to Brad through documents\nBrad communicates to Rachel through code\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • They probably aren’t, but you need to help them get there\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • This is a rational fear\nWe can assure Paul that we will build the right thing, not just to the original spec.\nPaul likely finds changes in requirements painful; help him see how agile helps\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Another rational fear\nCan’t comprehend how to spend time writing tests when manual tests are such a burden\nNeed the entire team helping with this\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Common objection of the hero coder\nSometimes rockstars don’t make the jump to whole team\nGood practices do slow us down at first; like learning to type correctly\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Members driven by desire to be accepted by others\nSerious issues are avoided\nTend to behave independently\nComfortable stage, but in avoiding conflict, not much gets done\nSupervisors are directive\n
  • Different ideas compete; open confrontation\nSome will focus on minutiae to avoid conflict\nContentious, unpleasant, possibly painful to those averse to conflict\nEmphasize tolerance and patience\nSupervisors are directive, but accessible\n
  • Team comes together with a mutual plan\nSome have to give up ideas for team to function\nAll team members take responsibility\nFocus is on team success\nSupervisors balance between participative and mildly directive\n
  • High-Performing Team functions as a single unit\nCompetent, Autonomous, and capable of handling decisions without supervision\nDissent is expected and allowed - handled according to team agreements\nSupervisors are participative; not authoritative\n
  • \n
  • Retrospective Prime Directive - Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.\nXP - Fix it when it breaks\nLean - Kaizan / Continuous Improvement\n
  • \n
  • \n
  • \n
  • \n
  • Story taken from backlog\nBA/QA/Dev review, adjust, agree - executable specs are created\nQA automates specifications while dev implements features\n
  • Story taken from backlog\nBA/QA/Dev review, adjust, agree - executable specs are created\nQA automates specifications while dev implements features\n
  • Story taken from backlog\nBA/QA/Dev review, adjust, agree - executable specs are created\nQA automates specifications while dev implements features\n
  • Story taken from backlog\nBA/QA/Dev review, adjust, agree - executable specs are created\nQA automates specifications while dev implements features\n
  • \n
  • Do I have a role?

    1. 1. Do I have a role? Michael “Doc” Norton @DocOnDev http://leandog.com doc@leandog.com
    2. 2. Yes!
    3. 3. Yes! NO!Well...
    4. 4. Yes, but...Agile is aboutwhole team
    5. 5. Individuals and Working Software Interactions Over Over Processes and Tools Comprehensive Documentation Customer Responding toCollaboration Change Over Over Contract Negotiation Following a Plan
    6. 6. Build projects around motivated The best architectures, individuals. Give them therequirements, and designs emerge environment and support they from self-organizing teams. need, and trust them to get the job done. The most efficient and effective At regular intervals, the teammethod of conveying information reflects on how to become moreto and within a development team effective, then tunes and adjusts is face-to-face conversation. its behavior accordingly.
    7. 7. So let’s meet the team
    8. 8. TheTeam
    9. 9. I am Laura,the Project Manager
    10. 10. I am Brad, theLead Developer
    11. 11. I am Rachel, the QA Lead
    12. 12. I am Paul, theBusiness Analyst
    13. 13. TheTeam
    14. 14. Requirements Working Code
    15. 15. Let’s talkabout roles onan agile team
    16. 16. Servant Leadership
    17. 17. Servant Leadership✦ Facilitate✦ Remove Roadblocks✦ Protect the Team✦ Team Manages Process
    18. 18. But...... I don’t think this team is ready to manage themselves
    19. 19. Lightweight Requirements
    20. 20. Lightweight Requirements ✦ Index Cards ✦ Story Mapping ✦ Progressive Elaboration ✦ In Order To, As A, I Want ✦ Communicate & Collaborate
    21. 21. But...... we’ll build the wrong thing
    22. 22. Executable Tests
    23. 23. Executable Tests✦ Write Tests First✦ Test Continuously✦ Automated Testing✦ Communicate & Collaborate
    24. 24. But...... we don’t have time to build tests
    25. 25. Collective Ownership
    26. 26. Collective Ownership ✦ Program in Pairs ✦ Test / Code / Refactor ✦ Continuous Integration ✦ Communicate & Collaborate
    27. 27. But...... you’ll slow me down
    28. 28. Let’s eliminate the silosRequirements Working Code
    29. 29. You can work together onrequirements
    30. 30. You can work together on automation
    31. 31. This won’t be easy.
    32. 32. But it’ll be worth it.
    33. 33. Tuckman’s Stagesof Group Development
    34. 34. Forming
    35. 35. Storming
    36. 36. Norming
    37. 37. Performing
    38. 38. We discuss stories in a“three amigos” meeting
    39. 39. We Inspect and Adapt
    40. 40. And...... the team makes good decisions while I help shepherd
    41. 41. And...... we build what we need as we go
    42. 42. And...... now everyone is involved in testing
    43. 43. And...... the whole team delivers in short cycles
    44. 44. Everyone has a roleWe are all team members Michael “Doc” Norton @DocOnDev http://leandog.com doc@leandog.com
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×