Strengthen your Pre-Project and Post-Project Process

Typically, an information technology project consists of three-phases:

• Pre-Project
• Project Execution Initiation - which starts with an explicit charter, Planning, Execution, Control and Close
• Post Project

While the Project execution phase, a waterfall or agile methodology brings extreme rigour, the same isn't true for neither Pre-Project nor post-project delivery. To add similar rigour to these two processes consider this:

Pre Project

• Target process to be Improved
• Unsolicited Lived Experiences of Staff and Customers who are impacted by the target process? ?
• Define Opportunity (Business Strategy, Technology Strategy, Top Level Process)
• Solicited Lived Experiences (focused engagement on specific subprocesses)
• Improved Process (Quick Wins, Tech Change, Transformational Change)
• Architecture Roadmap and Business Case

Project Execution

• Input from Pre-Project Work ( explicitly stated scope from the roadmap)
• Current Methodology- Initiation - develop charter in less than a day, Planning, Execution, Control and Close

Post Project

• Solicited and unsolicited lived experiences of customers and staff after the processes are changed
• Quantify the value of the improved processes

WhiteSparrow Labs and Launch Kawarthas are conducting an in-person workshop to showcase how to make the methods real with minimum disruptions to your current project delivery methods,

Explore and Register

All feedback and insight is welcome.