Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Project Closeout

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Activities in Phase 5
Phase 5 - Incremental Development, Testing, Deployment and Improvement
Content Model Relationship

Contents

Activity: Project Closeout

Objective

The Project Closeout activity is used to ensure we are constantly improving the MIKE2.0 Methodology and making the lessons learned and project assets (where appropriate) available as part of the open approach.

Major Deliverables

  • Project Assets (where appropriate)
  • Project Qual
  • Lessons Learned
  • Revisions to Overall Methodology

Tasks

Complete Project Case Study

Objective:

The project Case Study provides a summary of the project by listing major challenges, solution overview and the value delivered by the MIKE2.0 Methodology. Project Case Studies are critical aspects to the overall sales and delivery cycle.

Case Studies should be completed in a detailed and presentation overview form, showing the key aspects of the architecture.


Input:

  • Completed Project


Output:

Complete Project Lessons Learned

Objective:

To ensure mistakes from the past aren’t continually repeated, a review session should be scheduled to go through the completed projected. Unlike the Post-Implementation Review, this is an internal project team review. This review should cover positive and negative aspects of the project, on areas such as:

  • Use of MIKE2.0 methodology
  • Solution Approach
  • Engagement Management
  • Vendor Management

It should be noted that some of this information is sensitive and particular care should be taken when undergoing this process.


Input:

  • Completed project
  • Post-implementation review


Output:

  • Lessons Learned Document

Recommend Revisions or Extensions to MIKE2.0 Methodology

Objective:

The MIKE2.0 methodology should always be in a state of re-factoring and improvement, changing to meet the needs of our clients and align to new technologies. For major projects in particular, a review workshop should take place to propose if any of the materials should be added into the overall MIKE2.0 methodology. There will always be many Things to do to extend the methodology and users of MIKE2.0 need not wait until the completion of a project to work on these activities.

Input:

  • Completed Project
  • Project Deliverables
  • Lessons Learned Document


Output:

  • Revisions and Extensions to the MIKE2.0 Methodology

Core Supporting Assets

Yellow Flags

  • Less mature organizations may not see the need for all closeout sub-activities. The importance of proper closeout and its benefits should be stressed as part of the project.

Key Resource Requirements

Wiki Contributors
Collapse Expand Close