Make priorities explicit
When every request is urgent, teams cannot make informed tradeoffs. Start with a shared understanding of the outcome, the work needed next and the decisions that remain open.
Planning is a conversation about capacity, dependencies and uncertainty. Treat the plan as a useful guide that can be revisited when circumstances change.
Show the movement of work
A delivery board is useful when it reflects how work actually happens. Make blocked work visible and identify the decision or dependency needed to move it forward.
Scrum and Kanban offer practices that teams can adapt to their context. The important question is whether the team and stakeholders can understand progress and discuss problems early.
Connect governance to decisions
Status reporting should help people make decisions. Explain changes in scope, emerging risks and the support needed from stakeholders. Avoid substituting activity counts for an account of delivery progress.
JIRA and Confluence can support this shared understanding when workflows and documentation are kept relevant to the team. Tools should reinforce a useful process.
Use feedback to improve the process
Create room to examine what helped and what slowed the team down. Select a manageable improvement and revisit it, rather than generating a long list of actions that nobody owns.
Coaching and practical training help a team build the confidence to improve its own ways of working. Capability should remain with the people doing the work.
Back to all insights