Oct 15, 2022 8:50 AM
Replying to Thomas Walenta
...
Hi Ginny,
good advice given so far.
1. change your attitude from believing to knowing (by communicating, getting/giving commitments, documenting decisions)
2. if your sponsor is indeed the CIO, he should be able to give you his key requirements, probably based on pains - write them down, if you can, get a charter
3. with no process in place a key pain should be "portfolio visibility" which can be solved with a projects (and maybe project candidates) dashboard, but even that is not easy as you need (standardized) input from many stakeholders
4. limit the scope by only looking at the top 30-40 projects (20% have 80% impact) - you may call it MVP if you need
5. avoid tools as long as you can
6. avoid resource management as long as you can
7. define and plan your project with deadlines, should be less than 18 months induration
8. once you delivered your first product, start looking for the next pain, maybe "we have to many project ideas and try to do too many projects at a time (which often leads to staff burnouts and delays), so we need a decision process to start projects and which"
9. once you get to define the selection decision process, make sure those are NOT IT decisions (e.g. based on IT resource availability) but business decisions (strategic fit, funding, ..)
Good luck
Thomas