In project management having well thought-out steps is like having half-job done. Even if it looks easy from the first glance, real world examples proving the opposite — planning is an art.
During my career I switched domain and tech areas, though processes remained the same, as well as bottlenecks. Eventually, I came up with an ideal project template that fits any initiative no matter what the size or technology is.
Roadmap
- Requirements provided for technical review to immediate implementers. It should be a separate call which all stakeholders attend. The earlier docs reviewed, earlier next phase can start.
- Investigation phase started. All possible bumps on the road identified and discussed. It’s okay to allow investigation phase increase, so dev phase don’t. There is no ETA commitments yet, but premature estimation could be made .
I use to pretend I’m developing already here, that’s where questions raised from usually. As an outcome I’m getting solution proposal that builds base ground for further discussions. - Development phase kickoff, ETA set, bottlenecks resolved. Project could be transitioned to READY FOR DEV state.
- Development phase itself.
- QA. Should start some time before release, so it’s possible to fix bugs.
- Deploy & monitoring.
Usage notes
- Take as much time to investigate as needed
- Don’t be afraid to push back in case you need more time
I saw so much times when there were some blind spots left as “to check in process” and later it led to 2–3x time increase. Just don’t leave them to latter.
From product owner’s side it could be beneficial to provide requirements somewhat before previous project finish. So on the moment one project finished, next one is already on the developer’s plate at least in mind.
I use to switch contexts like this, so I don’t get tired by working only on one area.
P.S
And take vacations. That continuous project train can easily drain you out; take care about yourself first. You are the most important in your life, not work or manager’s review.
***
Upd (30.07.2024): One of potential issues on the very early phase of the project is developer’s lack of domain knowledge. Project manager should be aware of that and provide great introduction before kicking-off any other process.
