 WHY GOVERNANCE?
Before starting any major initiative: deployment, migration, or upgrade, start with your Governance Plan. Projects can kick off and run smoothly for weeks or months until unspoken configuration options need to be discussed and decisions made. Security risks need to be addressed. End user experiences may be looking less than ideal. Nobody knows who’s responsible for what... Cue the major project delays. “Those who cannot remember the past are condemned to repeat it.”  What is a Project Retrospective?
A project retrospective is an opportunity for project teams to reflect on the successes and challenges encountered during the project. It provides time for introspection, away from the frenetic demands of project delivery, during which the team can discuss and analyze the project’s challenges and identify actions to be taken to avoid these issues in the future. The retrospective is also an opportunity to build team cohesiveness and to celebrate the team’s successes. In short, the goal of the retrospective is to improve team performance between one project and the next. Organized as a structured workshop or meeting, retrospectives are typically held at the conclusion of a project, although they may also be held mid-project, following the completion of major milestones. The following questions are commonly asked and answered during a retrospective:
Nobody likes a failed project. Especially one as big as a cloud migration. Many people become so focused on crossing the finish line as soon as possible that they lose sight of the details that matter. If you want your project to succeed, you’ll need a solid foundation of business requirements and well documented processes in place. This will lead to better performance in the long term, and help your project succeed. Check out these 3 simple steps to help set you up for a successful cloud migration and happier stakeholders.  |
Archives
September 2021
Categories
All
Subscribe |
RSS Feed
|
5 Reasons Most Technology Projects Fail
|
