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.

Continuous Improvement

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Continuous implementation activities.jpg

The Continuous Improvement Activities of MIKE2.0 are focused on delivering incremental improvements to existing functionality. Continuous Improvement may involve minor changes or may initiate significant pieces of work. Significant pieces of work would generally involve taking the scope defined as part of Continuous Improvement and going back to Phase 3 for its implementation.

The Continuous Improvement Activities of MIKE2.0 cover:

Planning for Continuous Improvement is the key. Oftentimes projects stop funding after they have been implemented into production, or only set aside funding for warranty or future functional enhancements. Continuous Improvement should be explicitly planned for each implementation increment.

Wiki Contributors
Collapse Expand Close