Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Do I have a role?
Semelhante a Do I have a role? (20)
Mais de Doc Norton
Mais de Doc Norton (20)
Último
Último (20)
Do I have a role?
- 1. Do I have a role? Michael “Doc” Norton @DocOnDev http://leandog.com doc@leandog.com
- 2. Yes!
- 4. Yes, but... Agile is about whole team
- 5. Individuals and Working Software Interactions Over Over Processes and Tools Comprehensive Documentation Customer Responding to Collaboration Change Over Over Contract Negotiation Following a Plan
- 6. Build projects around motivated The best architectures, individuals. Give them the requirements, 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 team method of conveying information reflects on how to become more to and within a development team effective, then tunes and adjusts is face-to-face conversation. its behavior accordingly.
- 7. So let’s meet the team
- 8. The Team
- 10. I am Laura, the Project Manager
- 12. I am Brad, the Lead Developer
- 14. I am Rachel, the QA Lead
- 16. I am Paul, the Business Analyst
- 18. The Team
- 19. Requirements Working Code
- 20. Let’s talk about roles on an agile team
- 22. Servant Leadership ✦ Facilitate ✦ Remove Roadblocks ✦ Protect the Team ✦ Team Manages Process
- 23. But... ... I don’t think this team is ready to manage themselves
- 25. Lightweight Requirements ✦ Index Cards ✦ Story Mapping ✦ Progressive Elaboration ✦ In Order To, As A, I Want ✦ Communicate & Collaborate
- 26. But... ... we’ll build the wrong thing
- 27. Executable Tests
- 28. Executable Tests ✦ Write Tests First ✦ Test Continuously ✦ Automated Testing ✦ Communicate & Collaborate
- 29. But... ... we don’t have time to build tests
- 31. Collective Ownership ✦ Program in Pairs ✦ Test / Code / Refactor ✦ Continuous Integration ✦ Communicate & Collaborate
- 32. But... ... you’ll slow me down
- 33. Let’s eliminate the silos Requirements Working Code
- 34. You can work together on requirements
- 35. You can work together on automation
- 36. This won’t be easy.
- 37. But it’ll be worth it.
- 38. Tuckman’s Stages of Group Development
- 39. Forming
- 40. Storming
- 41. Norming
- 42. Performing
- 43. We discuss stories in a “three amigos” meeting
- 44. We Inspect and Adapt
- 45. And... ... the team makes good decisions while I help shepherd
- 46. And... ... we build what we need as we go
- 47. And... ... now everyone is involved in testing
- 48. And... ... the whole team delivers in short cycles
- 51. Everyone has a role We are all team members Michael “Doc” Norton @DocOnDev http://leandog.com doc@leandog.com
Notas do Editor
- \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