When assigning work to team members, there are multiple considerations:
- Training developers on unfamiliar code
- Ensuring each developer has work to do
- Ease of planning what should go into a sprint/PI
- How quickly an issue can be done by the developers that could do it
- Context sharing with other developers who will work on a feature/epic
- How detailed the design needs to be
- How hard it is to estimate
How affects:
- Confidence on when feature will be complete
- Training team members on code bases
- Time to approve changes
- Speed of development
- Likelihood of unplanned work
- Likelihood of work being completed in expected time frame (all needed scenarios, not causing problems)
- How uniform and easy to understand the code base is
- How sprint burn down charts look
- How many sprints are required to complete blocker chains
Posts
No comments:
Post a Comment