Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Dev Team Process
Ähnlich wie Dev Team Process (20)
Mehr von Hosam Aly
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Dev Team Process
- 1. DEV TEAM PROCESS EXAMPLES AND IDEAS
- 2. TEXT AGENDA ▸ General Direction ▸ Support Rota ▸ Meetings ▸ Review Process ▸ CI / CD ▸ Boards and Graphs ▸ Sponsor Coins
- 3. TEXT GENERAL DIRECTION ▸ Favour pushing issues to done ▸ Swarm over subtasks, work in parallel, unblock issues ▸ Pair programming when suitable ▸ helps with quality and knowledge sharing ▸ Protected learning / innovation time ▸ CI pipeline has high priority ▸ Deployment is protected; CI fails if schema is changed
- 4. TEXT SUPPORT ROTA ▸ Workday and Outside Hours rota ▸ 10:00 AM to 6:00 PM ▸ First and second lines of support ▸ Assumes shared knowledge ▸ Free to ask for help ▸ If both people remain busy for two days, something needs to be fixed
- 5. TEXT MEETINGS ▸ Process Retrospective (fortnightly), with votes ▸ What went well ▸ What didn’t go so well ▸ Questions ▸ Ideas and Learnings ▸ Impediments
- 6. TEXT MEETINGS ▸ Health Check (monthly) ▸ How well are we doing? ▸ What should we focus on improving? ▸ Hot spots over time
- 7. TEXT MEETINGS ▸ Team Session ▸ Presentation on something we learned, or ▸ Discussion of an issue (e.g. post-incident report) ▸ Sheet for wanted and offered topics ▸ Design Sessions ▸ Existing system design and architecture ▸ Upcoming feature design, breakdown, and estimation ▸ Moderators + booked meetings
- 8. TEXT REVIEW PROCESS ▸ Two pairs of eyes are required ▸ Could be a pair-programmer plus another person ▸ Another reviewer from a different team invited, and the link is shared publicly ▸ Reviewers are selected randomly; experts may be invited additionally ▸ Helps with knowledge sharing and generating ideas ▸ Important issues marked as defects ▸ Reviewer(s) may end up pairing with the developer(s) ▸ Be pragmatic about suggestions; avoid sunk cost fallacy
- 9. TEXT CI / CD ▸ Runs all project tests on every commit ▸ Runs inter-project integration tests before merging ▸ Independent repository with project versions ▸ Runs deployment tasks ▸ Keeps deployment log showing who, why, when, versions, etc.
- 10. TEXT BOARDS ▸ The board is a method of communication ▸ Shared knowledge ▸ Expressed interests ▸ Collaboration to Get Things Done ▸ Increased bus factor ▸ Historical perspective ▸ View for External Stakeholders ▸ Dev Board, Product Board, and Cross-Product Board
- 11. TEXT BOARDS ▸ The board is a tool for visualisation ▸ Sense of progress ▸ Relative priority ▸ Bottlenecks ▸ Capacity or Velocity, Burn-down chart, Cycle time, etc ▸ Always visible on TV ▸ In addition to production dashboards
- 12. TEXT DEV BOARD ▸ To Do ▸ In Progress ▸ Done
- 13. TEXT DEV BOARD ▸ To Do ▸ In Progress ▸ Deploy ▸ Done
- 14. TEXT DEV BOARD ▸ To Do ▸ In Progress ▸ Review, Applying Comments ▸ Deploy ▸ Done
- 15. TEXT DEV BOARD ▸ To Design ▸ In Design ▸ To Develop ▸ In Development ▸ Review, Applying Comments ▸ Deploy ▸ Done
- 16. TEXT PRODUCT BOARD ▸ New ▸ Discovery ▸ Accepted ▸ To Design ▸ To Develop ▸ In Progress ▸ Deploy ▸ Measure
- 17. TEXT CROSS-PRODUCT BOARD (EPICS) ▸ New ▸ Discovery ▸ Accepted ▸ Prioritised ▸ In Progress ▸ Deploy ▸ Measure
- 18. TEXT SPONSOR COINS ▸ Sponsors, i.e. external stakeholders, get a budget ▸ All sponsors meet (e.g. quarterly) to “purchase” dev time ▸ Sponsors may choose to lend each other to get stuff done