Work the Critical Path Into a Sprint Plan
Translate a critical-path calculation into a practical Sprint plan and RAID actions.
Five tasks remain before a customer pilot: API contract takes 1 day; UI build takes 2 days after contract; integration takes 2 days after contract; security review takes 1 day after integration; demo script takes 1 day and can happen anytime. Find the longest dependent chain, then protect it in the Sprint plan and RAID log. The common shortcut is to start the most visible work first, like UI polish or demo scripting, because it feels like momentum. That violates the critical-path principle: visible progress outside the longest chain will not protect the pilot date if the path predecessor is…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in