Search/Run a Complex Project with a Small Team in Short Cycles

Run a Complex Project with a Small Team in Short Cycles

Use for complex work that can't be fully planned ahead. It sets up a small team, one ordered work list, short fixed cycles with one goal each, a shared standard for done, and regular check-ins and reviews to adjust the plan and the way of working.

To use this AI rule
## Make Work Visible, Check It Regularly, and Adjust the Plan Complex work cannot be controlled by prediction alone. Create a repeating loop that turns current evidence into timely decisions. - Make work, outcomes, and important constraints visible to the people doing the work and the people receiving value. - Inspect progress and results at a steady cadence. - Adapt the plan or process promptly when evidence reveals a meaningful deviation. - Use forecasts to support decisions, never to replace observed results. Visibility without inspection does not improve control. Inspection without adaptation only identifies problems. Preserve the complete loop, or state clearly that the project is using a different control model. ## Form One Small Team That Decides How to Split Its Own Work Use one cohesive, cross-functional group focused on one outcome at a time. The group should contain or acquire the skills needed to deliver useful results and should decide internally who does what, when, and how. Keep responsibility for discovery, delivery, verification, stakeholder collaboration, and ongoing operation inside the same unit; do not split accountability into internal subteams or status hierarchies. Keep the unit small enough for direct communication and large enough to complete meaningful work. If growth requires multiple groups, keep them aligned through the same outcome, ordered work source, value authority, and quality standard. Reinforce behaviors that make empirical work possible: - commit to the shared outcome and support one another; - focus on the active cycle; - make work and difficulties open to examination; - treat contributors as capable professionals; - raise hard facts and address difficult problems. Use a sustainable pace so focus and consistency survive beyond a single cycle. ## Define Three Roles: One Priority Owner, the Doers, and a Helper Who Removes Blockers Define a few clear accountabilities while keeping the delivery unit jointly responsible for useful outcomes. The value steward is one accountable individual, not a voting committee. This person sets and communicates the long-term outcome, orders the work source, clarifies items, and maximizes delivered value. Tasks may be delegated, but accountability remains with the steward. Stakeholders seeking a priority change work through this role. The delivery practitioners create usable progress, maintain the cycle plan, uphold the shared quality standard, adapt the plan as evidence changes, and hold one another professionally accountable. The people who will perform the work own its estimation and implementation plan. The process facilitator improves the unit's effectiveness by coaching self-management, removing impediments, strengthening evidence-based planning, and keeping coordination sessions purposeful and bounded. This is a service and enablement role, not a command hierarchy. ## Keep Short, Fixed-Length Cycles and Protect Each Cycle's Goal Use fixed-length cycles that are short enough to limit cost, effort, and decision risk. Begin the next cycle immediately after the previous one so the project has a stable operating rhythm. Within an active cycle: - do not make changes that endanger its outcome; - do not lower the agreed quality standard; - refine future work as understanding grows; - clarify and renegotiate scope when necessary without silently changing the outcome. Shorter cycles create more opportunities to learn and correct course. End a cycle early only when its outcome has become obsolete, and assign that decision to an explicit value authority. Place planning, brief coordination, outcome review, and process improvement inside the cycle. Give each session a clear purpose and a maximum duration; shorten supporting sessions when the cycle is shorter. ## Plan Each Cycle Around Why, What, and How Complete cycle planning collaboratively and answer three questions: 1. Why is this cycle valuable? 2. What can be completed within it? 3. How will the selected work become a usable result? Set one cycle outcome before planning ends. It should explain the value being pursued while preserving flexibility in the exact work used to achieve it. Select work using current priority, past delivery evidence, upcoming capacity, and the shared quality standard. The delivery practitioners decide the implementation approach and decompose selected items far enough to support daily inspection. The resulting cycle plan should connect the outcome, selected work, and actionable delivery approach. Update it throughout the cycle as new facts emerge. ## Keep One Visible, Ordered Work List Keep one visible, ordered, evolving source for the work needed to improve the product or service. The value steward owns its clarity and ordering; the people who will do the work own its estimates. Refine the source continuously by splitting large items, adding the detail needed for a decision, and revising order or size as more is learned. Attributes may differ by domain, but every item should be understandable enough for the next commitment decision. Select work for a cycle only when the delivery unit can reasonably complete it under the current quality standard. The active cycle plan then becomes the real-time view of why the work matters, what was selected, and how the unit intends to deliver it. Do not run multiple hidden priority lists. Competing sources weaken transparency and make trade-offs impossible to inspect. ## Set a Shared Quality Standard for When Work Counts as Done Treat progress as an integrated, verified, usable step toward the long-term outcome. Each completed step should work with prior results rather than exist as an isolated demonstration. Delivery may occur before a scheduled review. The review is a learning point, not a release gate. Define a shared completion standard that states the required quality measures. Work that does not meet the standard is not complete, cannot be represented as delivered value, and returns to the ordered work source for future consideration. Use organization-wide standards as the minimum where they exist. If several delivery groups work on the same product, they must share and follow the same completion standard. ## Run Daily Check-ins and Reviews of Results and the Way of Working Use a brief daily coordination session to inspect progress toward the cycle outcome and produce an actionable plan for the next working period. Let the delivery practitioners choose the format. They may adapt the plan at any time; the session is not their only opportunity. Use the outcome review as a working session with relevant stakeholders. Examine the usable result, changes in the environment, and progress toward the long-term outcome, then update future priorities together. Do not reduce this session to a presentation. Use the process review to examine people, interactions, methods, tools, quality practices, and assumptions. Identify what helped, what failed, and why. Apply the most valuable improvement as soon as practical, including it in the next cycle when useful. Schedule these inspection opportunities consistently so they create rhythm and reduce the need for additional status meetings.