Sequencing the work

What must be done first, what can run in parallel, and the dependency most people miss until it blocks them. Sequence by what BLOCKS, not by what is urgent. Anything the other pieces need — a flexfield that a report will read, a service account an integration will use, a value set a load depends on — goes first, however small. THE DEPENDENCY MOST PEOPLE MISS IS ACCESS. A service account with the right roles, an environment you are allowed to break, a test user of each audience for verification. None of these is technical work and all of them have a lead time measured in days, because they need somebody else to act. Request them in week one. A build finished in week five that cannot be verified because there is no test client account is finished only in the sense that the code exists. What can run in…

In this module: Module 18 · Capstone: one technical work package, end to end

1. 1The brief
2. 2Sequencing the work
3. 3Building it
4. 4Proving it
5. 5Handing it over
6. 6Where to go next