Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (11)
Semelhante a Agile Roles: where does everyone fit in an agile organization
Semelhante a Agile Roles: where does everyone fit in an agile organization (20)
Mais de Wajih Aslam
Mais de Wajih Aslam (12)
Último
Último (20)
Agile Roles: where does everyone fit in an agile organization
- 1. Agile Roles where does everyone fit in an agile organization Wajih Aslam Agile Coach
- 2. Who we are?
- 3. How to collaborate with us?
- 4. Meetup # 1 - Recap
- 5. Meetup # 2 - Recap
- 6. Agile Principles About Teamwork ❏ Business people and developers must work together daily throughout the project. ❏ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ❏ The best architectures, requirements, and designs emerge from self- organizing teams.
- 7. Agile is a team approach ● Self organizing teams ● Cross functional teams ● Motivated Teams https://www.mountaingoatsoftware.com/blog/self-organizing-teams-are-not-put-together-randomly https://www.mountaingoatsoftware.com/blog/cross-functional-doesnt-mean-everyone-can-do-everything
- 9. Scrum Roles ● Product Owner ● Scrum Master ● Development Team (Developers, QA, Analyst, Architect, UX, DevOps)
- 10. XP Roles ● Programmer ● Customer ● Tester ● Tracker ● Coach ● Consultant ● Manager
- 11. Kanban Roles ● No specific roles defined in KANBAN
- 12. Manager VS Leader ● Drive vs Coach ● Taking Decisions vs Facilitating Decisions ● Managing people vs Managing Work ● Monitor vs Trust ● Extrinsic motivation vs Intrinsic motivation ● Develop products vs Develop team who develop product
- 14. Supporting Function ● Leadership ● Mentors ● HR ● PMO
- 15. Thanks! ● https://meagile.com/ ● https://www.youtube.com/meagile ● https://www.slideshare.net/agileme ● https://twitter.com/agileme ● https://www.facebook.com/AgileMi ddleEast/
Notas do Editor
- Name, Designation, Company. My Topic
- Introduction Wajih / Rasmus Ask Introduction to audience … name, roles, company Introduction Agile ME
- Meetup, slack, Conference, Discounts Meetup attendance
- Agility – Ability to move quickly Business Agility Agile Manifesto and principles What value we are getting from agile Doing VS Being Agile
- Scrum Basic – Sprints, Events, Team Size, Work Increment, ROI (early value) Kanban Basic – Flexibility, Certainty, WIP limit Scaling – Why scaling: What happens when team size increases
- Our conclusion is agile is a team approach. Which kind of team we need to be successful in agile environment. Self-Organizing Team: The best architectures, requirements and designs emerge from self-organizing teams. It’s the Ability, every human being have it. Encourage Shared Responsibility and Decisions Believe on Collected wisdom Things out of responsibility of the self-organizing team Goal Team organization HR etc. Cross functional Team: Business people and developers must work together daily. Varity of skills people Enough skills to do their job without external dependencies Not every member is cross functional May have specialist Imagine the team of 10 people (Mike Cohn Example) Component vs functional teams Motivation: Build projects around motivated individuals. Autonomy Mastery --- Seeking Knowledge – continuous improvement --- Myth about agile about skills Purpose --- Story Why cutting woods Daniel Pink Reference: Carrot and tick not works for agile.
- Balance between autonomy and alignment – Spotify
- Product Owner Set the product Vision and direction Groom the stories with the team Prioritize the backlog items Maximize the value of team work Define Sprint Goal Development Team Pull the work from backlog in sprint Cross functional team does end to end development work T shaped team Scrum Master Guide the team in scrum practices Guide the product owner about Remove Impedance
- Developers: Decide what to do Write tests Code Reviews Customer: What to do Write user stories Decision Maker Confident Tester: Helping Customer to write functional test cases Runs functional tests Tracker: Monitoring Estimates Get information without interruptions Coach: Process keeper Consultant and Managers: Supporting Roles
- How team works in Kanban. WIP limit. Resolve Bottlenecks. Visibility
- Spotify Engineering culture, Tribes, Chapter Guild Bottom Up Approach, Shu Ha Ri