Most linked-to pages

Showing below up to 50 results in range #1 to #50.

1. Minimise unnecessary complexity‏‎ (21 links)
2. Organise around value streams‏‎ (21 links)
3. Maximise Team autonomy‏‎ (20 links)
4. Favour Teams with broader Business Domain Competence‏‎ (20 links)
5. Favour Teams with broader Solution Accountability‏‎ (20 links)
6. Create a Learning Organisation‏‎ (19 links)
7. Maximise engagement‏‎ (19 links)
8. Maximise team empowerment and localised decision making‏‎ (19 links)
9. Create the environment for people to thrive‏‎ (18 links)
10. Foster a high trust environment‏‎ (18 links)
11. Minimum Viable Product Owners‏‎ (16 links)
12. Limit Team Mental Workload‏‎ (16 links)
13. Support autonomy with clear boundaries‏‎ (16 links)
14. Shared context improves decisions‏‎ (15 links)
15. Create clarity of purpose‏‎ (13 links)
16. Product solution design is driven from within development teams‏‎ (13 links)
17. Self-managed teams‏‎ (12 links)
18. Cultivate learning between teams‏‎ (12 links)
19. Catalyst for change‏‎ (11 links)
20. End-to-End Product‏‎ (11 links)
21. Evolutionary over revolutionary change‏‎ (11 links)
22. Maximise the Scope of Product Increment‏‎ (11 links)
23. Invest in quality‏‎ (11 links)
24. Technical leaders as coaches, mentors and community leaders‏‎ (10 links)
25. Each team "sees" exactly one Product Owner‏‎ (10 links)
26. Avoid Components‏‎ (10 links)
27. Limit Product Owner Mental Workload‏‎ (10 links)
28. Involve those affected by change‏‎ (9 links)
29. Leadership supports rather than drives the work‏‎ (9 links)
30. Use the Definition of Done as an enabling constraint‏‎ (9 links)
31. Self-managed Team of Teams‏‎ (9 links)
32. Amplify Speed and Quality of Learning Cycles‏‎ (8 links)
33. Provide an impediment removal service‏‎ (8 links)
34. Align towards business synergies‏‎ (8 links)
35. Start small and scale success‏‎ (8 links)
36. Outcome is the primary measure of success‏‎ (8 links)
37. The Product Owner is accountable for sustained end value‏‎ (7 links)
38. Are lean practitioners‏‎ (7 links)
39. The Teams' Perspective‏‎ (7 links)
40. Scale only when you need to‏‎ (7 links)
41. Architectural cohesion‏‎ (7 links)
42. Favour teams with maximised cognitive diversity‏‎ (7 links)
43. The Change Perspective‏‎ (6 links)
44. Own your own approach‏‎ (6 links)
45. Collective responsibility for complete product development‏‎ (6 links)
46. Accidental Complexity‏‎ (5 links)
47. Collective accountability in case of Product Ownership Group‏‎ (5 links)
48. Craft‏‎ (5 links)
49. Optimise the system of work for the majority of cases rather than the exceptions‏‎ (5 links)
50. Reduce factors increasing product complexity‏‎ (5 links)