1. MoV® Foundation courseware
2. MoV® consists of: 7 Principles, 7 Processes, 7 Roles, 12 Documents, 18 Techniques (3 MoV specific, 15 common).
2.1. Download: Best Management Practice - MoV Launch presentation [01.08.2010]
3. MoV® Principles (7)
3.1. What are principles?
3.1.1. Principles are factors that underpin MoV®.
3.1.2. Principles are universally applicable statements.
3.1.2.1. Principles are generic principles - the way in which they are applied must be tailored to suit the organizational circumstances, whilst ensuring the underlying rationale is maintained.
3.1.2.2. Prainciples are the common, universal and high-level factors that underpin success.
3.1.2.3. They provide guidance to organizations.
3.1.2.4. They guide the organization on what to aim for.
3.2. 1. Align with organizational objectives
3.2.1. MoV® applications are fully aligned with the organization’s strategic objectives.
3.2.2. A consistent approach is applied across all projects and programmes.
3.3. 2. Focus on functions and required outcomes
3.3.1. Focus on functions and required outcomes, in terms which clearly state what value means for the organisation .
3.3.2. MoV® focuses on the functions that are necessary and sufficient in order to deliver the required programme and project outcomes and outputs in terms that clarify what value means for the organization, so providing the basis for making decisions that lead to maximum value.
3.3.3. We need to work out what we are trying to achieve before we start thinking about what to deliver.
3.3.4. supported by
3.3.4.1. Product functions (not outcomes or outputs)
3.3.4.2. Value Drivers
3.3.4.3. Value Profiles
3.3.4.4. Value Trees
3.3.4.5. Function Analysis System Technique (FAST)
3.4. 3. Balance the variables to maxinmize value
3.4.1. MoV® engages with all key stakeholders, reconciling their objectives to balance benefits and their delivery against the total use of resources, thereby maximizing value.
3.4.2. Effective stakeholder engagement will identify differing needs, to allow a balance of benefits to be defined that is acceptable to everyone.
3.4.3. supported by
3.4.3.1. Engegement of stakeholders
3.4.3.2. Reducing subjectivity
3.4.3.3. Balancing the use of resources
3.4.3.4. Balancing benefits realized against use of resources
3.5. 4. Apply MoV® throught the investment decision
3.5.1. MoV® is applied through all stages of the total lifecycle of the programme or project. Its focus will evolve as it moves from stage to stage and progress should be continually monitored
3.6. 5. Taylor MoV® activity to suit the subject
3.6.1. MoV® is tailored to suit the project’s environment, size, complexity, criticality and risk.
3.6.2. A small and simple project is unlikely to require the same level of effort as a complex one.
3.7. 6. Learn from experience and improve
3.7.1. MoV® applications encourage learning from experience and improvement by recording previous experience, creating an audit trail of decisions and actions and sharing lessons across all projects.
3.7.2. Build on the good experiences and avoid repeating mistakes.
3.7.3. supported by
3.7.3.1. Invidual improvement
3.7.3.2. MoV® Process improvement
3.7.3.3. Organizational maturity improvement
3.8. 7. Assign clear roles and responsibilities and build a supportive culture
3.8.1. MoV® applications are supported by clearly defined roles and responsibilities. The organizational structure should engage the business, user and supplier stakeholder interests to build a supportive, value-adding culture.
3.8.2. Without commitment and buy-in, MoV is unlikely to be wholly successful.
4. MoV® Processes (7)
4.1. 1. Frame the programme of project
4.1.1. Goal
4.1.1.1. Understand the rationale behind the project or programme and the objectives to achieve.
4.1.2. Involves gaining an understanding of the objectives and issues that need to be addressed, taking into account the organizational context and external factors. Information gained can be used to support or challenge the need for the project.
4.1.3. Activities
4.1.3.1. Initial briefing meeting
4.1.3.1.1. As soon as a project / programme has been identified for the application of MoV®, Senior MoV® Practitioner, or MoV® Study Leader if identified, should meet ith key project stakeholders to stablish the requirements for the MoV® Project Plan.
4.1.3.2. Informing the business case
4.1.3.2.1. The main objective of an MoV® Study at the outset, or start up, of a programme or potential project is to strengthen existing information
4.1.3.2.2. An MoV® Study at this stage may be used to inform an OGC Gateway 0 or 1 Review
4.1.3.3. Stakeholder analysis
4.1.3.3.1. In MoV®, stakeholder mapping is used to ensure that the appropriate stakeholders are consulted or involved in the MoV® processes
4.1.3.3.2. Stakeholders are grouped according to their degree of influence (or power)
4.1.3.3.3. Stakeholders with less power but great interest can form strong allies
4.1.3.4. Use of a value profile to inform programme and project objectives
4.1.3.4.1. There is no point in starting a project unless there is agreement on its purpose.
4.1.3.4.2. MoV® helps to identify the primary Value Drivers and relate them to the project objectives using a weighted Value Tree, this technique, known as Value Profiling
4.1.3.5. Developing the MoV® Project Plan
4.1.3.5.1. MoV® Project Plan will describe the purpose of a series of MoV® Studies to be undertaken throughout the project and how they will be implemented
4.1.3.5.2. Identify suitable candidates to lead and participate in the MoV® Studies
4.1.3.5.3. Prepare specific management responses to value-improving proposals (VIPs)
4.1.3.5.4. The risk of delay in authorizing the implementation of these proposals should be minimized
4.1.3.5.5. The use of the MoV® Project Plan ensures that all participants understand the need for each study and what improvement is sought
4.1.3.6. Responding to changes in the business case
4.1.3.6.1. If the business case changes, the MoV® Project Plan must also change in order to ensure that the value profile reflects the changed needs of the business.
4.1.3.7. Specialist applications
4.2. 2. Gather Information
4.2.1. Goal
4.2.1.1. What are the expectations from the MoV® Study, who do we need on the MoV® Study Team, who are the stakeholders, what are their needs.
4.2.2. Involve as many different stakeholders as possible in order to understand the expectations from the project under study, identify suitable team members, understand stakeholders’ needs and other project-related information.
4.2.3. Activities
4.2.3.1. Briefing meeting
4.2.3.1.1. All information needed for MoV® Study Handbook, acts as a breefing document
4.2.3.2. Team selection
4.2.3.2.1. Knowledge + issues to be addressed + skills
4.2.3.2.2. Collaboration
4.2.3.3. Consulting with stakeholders
4.2.3.4. Research and precedent
4.2.3.5. Scoping
4.3. 3. Analyse Information
4.3.1. Goal
4.3.1.1. Enrich the gathered information, use techniques like FAST to understand the purpose and analyse alternative ways of performing or delivering the functions.
4.3.1.2. Analyzing the gathered information to form useful input to the MoV® Study.
4.3.2. The MoV® guide gives details of some of the more commonly used techniques, such like FAST or Value Trees.
4.3.3. Function analysis is a key feature of MoV® and is based on the following fundamental questions:
4.3.3.1. What is the purpose? Until you understand the purpose of something, its value cannot be assessed.
4.3.3.2. How else could this be achieved? Once you understand the purpose, alternative ways of performing or delivering the function may be identified, which may perform better or be less costly.
4.3.4. Activities
4.3.4.1. Function analysis
4.3.4.2. Resource analysis
4.3.4.3. Function cost analysis
4.3.4.4. Benchmark analysis
4.4. 4. Process Information
4.4.1. Goal
4.4.1.1. Working with the MoV® Study Team to use the above input information to develop innovative and Value-Improving Proposals (VIPs).
4.4.2. The MoV® Study Team uses the information to explore alternative proposals to improve value, typically through a series of meetings and workshops. New ideas will arise and often it is found that a function is not actually needed, so can be eliminated from the proposal.
4.4.3. Activities
4.4.3.1. Preparation
4.4.3.2. Facilitation
4.4.3.3. Creativity and innovation
4.5. 5. Evaluate and Select
4.5.1. Goal
4.5.1.1. Selecting the proposals that have most potential for practical and beneficial implementation.
4.5.2. The MoV® Study Team evaluates the merits of the different options by assessing their performance against value drivers, to identify those that add most value.
4.5.3. Balance the variables to maximize the value.
4.5.3.1. Balancing the needs of different stakeholders
4.5.3.2. Balancing the use of (often scarce) resources
4.5.3.3. Balancing the benefits expected against the cost of money and resources to deliver
4.5.4. Activities
4.5.4.1. Idea selection
4.5.4.2. Option selection
4.5.4.3. Cost benefit analysis
4.6. 6. Develop Value-Improving Proposals (VIPs)
4.6.1. Goal
4.6.1.1. Working up the outline proposals into fully developed recommendations for presentation to decision-making management.
4.6.2. The MoV® Study Team develops the selected ideas into value-improving proposals for decision and implementation.
4.6.3. Activities
4.6.3.1. Proposal development formats
4.6.3.2. Peer review
4.6.3.3. Balancing the benefits and use of resources
4.6.3.4. Value metrics
4.6.3.5. Cost estimation
4.6.3.6. Assessing time impact
4.6.3.7. Assessing performance impact
4.6.3.8. Scenario building
4.6.3.9. Specialist applications
4.7. 7. Implement and Share Outputs
4.7.1. Goal
4.7.1.1. Develop the plan, implement accepted Value Improvement Proposals (VIPs), monitor progress, gather lessons learned and share for continuous improvement.
4.7.2. A plan for implementing the selected option is developed and implemented.
4.7.3. A benefits management process should be implemented to track achievement of expected benefits.
4.7.4. Ideally, the measures used to assess adding value will be the same as those already used by the project to track progress and assessment of benefits.
4.7.5. Activities
4.7.5.1. Developing the proposal implementation plan
4.7.5.2. Incentivizing delivery of value
4.7.5.3. Monitoring progress
4.7.5.4. Reporting
5. MoV Additional techniques (a.k.a. MoV® Toolbox)
5.1. Methods and tools that MAY be used in the application of MoV®.
5.2. Business process re-engineering
5.3. Conjoint analysis
5.4. Cost estimation
5.5. De Bono P/M/I
5.6. Delphi
5.7. Dots
5.8. Earned value analysis or management
5.9. Elementary skills gap analysis
5.10. Excursions and metaphors
5.11. Facilitation
5.12. Five Ws and an H
5.13. Function Analysis System Technique (FAST)
5.14. Function priority matrix
5.15. HM Treasury’s Green Boo
5.16. Informationgathering methods
5.17. Issues generation and analysis
5.18. Kano quality model
5.19. Knowledge capture and dissemination
5.20. Lean principles and Lean Sigma
5.21. Managing difficult people
5.22. Net present value
5.23. Pareto
5.24. Peer review
5.25. Presentation techniques
5.26. Report writing
5.27. Risk management
5.28. SCAMPER
5.29. Scenario building
5.30. Simple Multi-Attribute Rating Technique (SMART)
5.31. Soft systems methodology (SSM)
5.32. Stakeholder analysis
5.33. Stakeholder identification
5.34. Strategic choice approach
5.35. Strategic options development and analysis (SODA)
5.36. Sustainability and triple bottom line
5.37. SWOT analysis
5.38. Systems thinking
5.39. Target costing
5.40. T charts
5.41. Team-building
5.42. Theory of constraints
5.43. Tracking benefits realization
5.44. Value metrics
5.45. Warm-up exercises / ice breakers
5.46. Workshop / study toolkit
6. MoV® Documents (12)
6.1. Briefing Meeting Agenda (A.1)
6.1.1. What is it?
6.1.1.1. The objectives of a briefing meeting are to understand the project, the type of study that is needed, study logistics and how any feedback arrangements will be handled.
6.2. Communications Checklist (A.2)
6.2.1. What is it?
6.2.1.1. Visualize the exact circumstances in which the information is to be received. This will then suggest the best way to receive it.
6.3. Equipment List for an Effective Study / Workshop (A.3)
6.3.1. What is it?
6.3.1.1. The majority of studies will require that presentations are made, and all will need some equipment to record discussions and decisions. This checklist covers the most common requirements
6.4. Invitation to Join the Study Team (A.4)
6.4.1. What is it?
6.4.1.1. Certain information is essential to ensure that participants are well prepared from the start
6.5. Option Evalutaion Marix (A.5)
6.5.1. What is it?
6.5.1.1. Often it is necessary to choose between a few options to assess which provides best value for money. Table A.1 in official MoV publication provides a format for doing this
6.6. Plan the Study (A.6)
6.6.1. What is it?
6.6.1.1. Generic plan of activities for a single study will generally include the following
6.7. Recording Idea Selection (A.7)
6.7.1. What is it?
6.7.1.1. A method is needed to capture all ideas and evaluate them, so that a proportion can be selected for further development
6.8. Reporting Study Outputs (A.8)
6.8.1. What is it?
6.8.1.1. The outcomes of an MoV® study must always be recorded and fedback to its sponsors
6.8.1.2. Outline for a generic MoV® report, with all content that should be considered against its audience
6.9. Scoping the Study (A.9)
6.9.1. What is it?
6.9.1.1. The study scope documents the name and purpose of the study and lists the study sponsor and stakeholders. It also lists assumptions, constraints and givens.
6.10. Study or Workshop Handbook (A.10)
6.10.1. What is it?
6.10.1.1. MoV® Study Team will need certain guidelines and information
6.10.1.2. The MoV® Study Leader will use some of this information to decide how best to conduct the study
6.11. Value-improving Proposal Forms (A.11)
6.11.1. What is it?
6.11.1.1. Some sort of standard form is necessary for summarizing and presenting the outputs from a value study in a way that allows them to be compared.
6.11.1.2. They can be prioritized against available funds
6.12. Value Improvement Tracking Report (A.12)
6.12.1. What is it?
6.12.1.1. Monitoring progress in implementing the agreed changes following a MoV® study
6.12.1.2. According to MoV® it saves a great deal of time if this is run in a spreadsheet, with dropdown lists of the value drivers and owners etc.
6.12.1.3. it will be necessary to score how easy it is to implement, the likely capital investment (later, this will be the amount actually used) and the operating cost (whether or not this is a measure)
7. MoV® Official publications
7.1. Management of Value
7.1.1. ISBN-13: 978-0113312764
7.1.2. Published: 2010
7.1.3. Pages: 161
7.1.4. http://www.amazon.co.uk/Management-value-Michael-Dallas/dp/0113312768/
7.1.5. The most important, key position on MoV® preparing for exams Foundation and Practitioner.
7.2. An executive guide to value management
7.2.1. ISBN-13: 978-0113312795
7.2.2. Published: 2010
7.2.3. Pages: 48
7.2.4. http://www.amazon.co.uk/An-executive-guide-value-management/dp/0113312792
8. MoV® - process based standard and framework (not methodology) for general (not industry specific e.g. IT or Engeenering) Value Management. MoV® is one of the 12 recognized globally and practically proven management standards from AXELOS® Global Best Practice family of UK standards.
8.1. MoV® V1 was published in 04.2010.
8.2. How MoV® fits into AXELOS® Global Best Practices family of UK standards.
8.2.1. MoV® in AXELOS® Global Best Practices family
8.3. AXELOS® Global Best Practices family of standards from UK.
8.3.1. PRINCE2® Agile
8.3.1.1. see PRINCE2® Agile mind map
8.3.2. ITIL®
8.3.2.1. see ITIL® mind map
8.3.3. M_o_R® - Management of Risk
8.3.3.1. see M_o_R® mind map
8.3.4. MoV® - Management of Value
8.3.4.1. see MoV® mind map
8.3.5. MoP® - Management of Portfolios
8.3.5.1. see MoP® mind map
8.3.6. MSP® - Managing Successful Programmes
8.3.6.1. see MSP® mind map
8.3.7. PRINCE2® - PRojects IN Changing Environments
8.3.7.1. see PRINCE2® mind map
8.3.8. P3O® - Portfolio, Programme and Project Office
8.3.8.1. see P3O® mind map
8.3.9. yet remember - "In reality there are no such things as best practices. There are only practices that are good within a certain context."
8.4. Since 2000 the Office of Government Commerce (OGC), former owner of PRINCE2® (and other Best Management Practices) has been the custodian of the portfolio on behalf of UKG. In June 2010 as a result of UKG reorganisation the Minister for the Cabinet Office announced that the PRINCE2® functions have moved into Cabinet Office.
8.4.1. AXELOS are a new joint venture company, created by the Cabinet Office on behalf of Her Majesty’s Government (HMG) in the United Kingdom and Capita plc to run the Best Management Practice portfolio, now called AXELOS Global Best Practice
8.4.2. https://www.gov.uk/government/publications/best-management-practice-portfolio/about-the-office-of-government-commerce
9. MoV® Official resources
9.1. MoV® sample exams, available online
9.1.1. MoV® Foundation
9.1.1.1. http://online.apmg-exams.com/index.aspx?subid=99&masterid=33
9.2. MoV® examination syllabus
9.2.1. EN
9.2.1.1. http://www.mov-officialsite.com/nmsruntime/saveasdialog.aspx?lID=78&sID=26
9.3. MoV® glossary
9.3.1. EN
9.3.1.1. http://www.axelos.com/gempdf/Axelos_Common_Glossary_2013.pdf
9.4. MoV® White Papers
9.4.1. The basics: Management of Value
9.4.1.1. http://www.axelos.com/gempdf/The_Basics_MoV.pdf
9.4.2. Business benefits of implementing MoV™
9.4.2.1. http://www.axelos.com/gempdf/Business_Benefits_of_Implementing_MoV.pdf
9.5. MoV® website
9.5.1. http://www.mov-officialsite.com/
10. MoV® Roles and Responsibilities (7)
10.1. Executive Board
10.1.1. Full alignment of MoV® activities and processes with organizational objectives
10.2. MoV® Representative on Executive Board
10.2.1. Promote MoV®
10.2.2. Likely to be the sponsor who represents MoV®
10.3. MoV® Board (or Steering Group)
10.3.1. Oversee MoV® implementation
10.4. Senior MoV® Practitioner
10.4.1. Responsible for implementing the MoV® Policy and contribute to its development and updating from time to time.
10.4.2. The individual charged with leading the implementation of the MoV® Implementation Plan.
10.4.3. Person responsible for managing the MoV® effort.
10.4.4. Experienced in MoV, have both the knowledge and skill to apply it. (unlikely to already exist in the organization, offen consultant).
10.4.5. Will be to undertake activities and publish material to build a culture within the organization that understands and supports the concept of maximizing value both for the organization and the project stakeholders.
10.4.6. Will be actively engaged in all aspects of the MoV® programme and must demonstrate leadership and competence in the subject to inspire and motivate all those who are involved.
10.4.7. Creates MoV® Policy Implementation Strategy.
10.4.8. Mentoring and coaching.
10.4.9. Import MoV® skills and knowledge.
10.5. MoV® Study Leaders (or Study leaders)
10.5.1. Lead MoV® studies
10.5.2. Help Secion MoV® Practitioner in activitier selated witn MoV® implementatio,
10.6. MoV® Study Team (or Study Team)
10.6.1. Participate in studies
10.6.2. Low level MoV® members
10.7. Support Office (if there i one)
10.7.1. Provide data for use in studies and communicate results and learning
10.7.2. Trainings and MoV® promotion
10.7.3. Suggests and implemnets MoV® related software
11. MoV® Techniques (18)
11.1. Methods and tools used in the application of MoV®.
11.2. MoV® specific techniques (3)
11.2.1. Function Analysis
11.2.1.1. What is it?
11.2.1.1.1. Why + How
11.2.1.1.2. Function Analysis challenges the assumptions most people make about how a product or service satisfies a need.
11.2.1.1.3. Asking How and Why a function accomplishes the need.
11.2.1.1.4. As used in MoV®, function analysis is very closely focused on customer needs and wants.
11.2.1.1.5. The fundamental logic underlying all function analysis is to ask ‘Why (do we want to do this)?’ to move from lower-order functions to higherorder functions and to ask ‘How (do we propose to do it)?’ to move in the opposite direction.
11.2.1.2. Identification of functions (at the heart of value management) of products, processes, projects or services.
11.2.1.3. Determines what functions are delivered, i.e. what they do or must do, not what they are (avoiding solution mode).
11.2.1.4. There are 2 main methods of Function Analysis:
11.2.1.4.1. Function Analysis System Technique (FAST) diagrams
11.2.1.4.2. Value Trees (a.k.a. Objectives hierarchy) and useful derivatives
11.2.2. Function Cost Analysis (FCA)
11.2.2.1. Cost / Worth (a.k.a. ‘cost to function’)
11.2.2.1.1. What is it?
11.2.3. Value Engineering (VE) / Analysis
11.2.3.1. What is it?
11.2.3.1.1. Recognized techniques for generating alternative actions to improve value through balancing function and cost without detriment to quality
11.2.3.1.2. Original process introduced in the USA shortly after the II World War
11.2.3.1.3. Primary purpose is to improve value in an existing design or set of circumstances by studying in detail 2 fundamental questions:
11.2.3.2. Most commonly used in MoV®
11.2.3.3. Improving value in an existing design
11.2.3.4. VE comprises 8 steps, usually referred to as phase
11.2.3.4.1. Information phase
11.2.3.4.2. Analysis phase
11.2.3.4.3. Creative (or speculation) phase
11.2.3.4.4. Evaluation phase
11.2.3.4.5. Development phase
11.2.3.4.6. Presentation phase
11.2.3.4.7. Implementation phase
11.2.3.4.8. Follow-up phase
11.2.3.5. VE study will be arranged and facilitated by a skilled MoV® Study Leader
11.2.3.6. At the end of the workshop or shortly thereafter, the team will present their findings and recommendations to a decision-making panel and agree an implementation plan
11.2.3.7. Value-improving proposals (VIPs) will then be implemented by the project team
11.3. Common techniques used in MoV® (15)
11.3.1. techniqes for information analysis
11.3.1.1. Benchmarking
11.3.1.2. Process mapping
11.3.1.2.1. Uses flow charts to review steps in processes.
11.3.1.2.2. Identifies processes in a diagrammatic format in a step-by-step manner.
11.3.1.2.3. Often used in manufacturing of system type processes.
11.3.1.2.4. Used to identify omissions or superfluous items in the process for correction.
11.3.1.3. Root cause analysis
11.3.1.4. Discounted cash flow analysis
11.3.2. techniques for idea generation
11.3.2.1. Brainstorming (a.k.a. mind showering)
11.3.2.1.1. Idea generation that focuses on creation of ideas by volume (no judging).
11.3.2.1.2. Allows a large volume of ideas to be generated in a short period.
11.3.2.1.3. Also strives to ensure all parties are involved - no ideas are discounted initially (later evaluation and filtering undertaken).
11.3.3. techniques for evaluation and option selection
11.3.3.1. Option evaluation matrix
11.3.3.2. Allocation to categorie
11.3.3.3. Idea selection matrix
11.3.4. techniques for weighting
11.3.4.1. Paired comparisons
11.3.4.2. Points distribution
11.3.5. techniques for developing value-improving proposals (VIPs)
11.3.5.1. Cost benefit analysis (CBA)
11.3.5.1.1. Used to analyse the costs of implementing something compared to the benefits to be
11.3.5.1.2. Used to analyse the costs of implementing something compared to the benefits to be achieved.
11.3.5.1.3. Assists business case submissions.
11.3.5.1.4. Often used in VM on procedure or process type projects.
11.3.5.1.5. Can be combined with other tools; for example, process mapping, option selection.
11.3.5.2. Decision-building meeting
11.3.6. techniques for implementing VIPs and follow-up
11.3.6.1. Implementation plans
11.3.6.2. Feedback
11.3.6.3. Tracking benefits
12. Embedding MoV® into an organization
12.1. MoV® Policy
12.2. Plan For Implementing the MoV® Policy
12.3. Trainings
12.3.1. Awareness training
12.3.2. Foundation-level training
12.3.3. Practitioner-level training
12.3.4. Advanced study leader training
12.4. MoV® Study Leader's Handbook
12.4.1. How to apply MoV® to projects and programmes
12.5. Data Capture Feedback
12.6. Monitoring and measuring the benefits
12.6.1. MoV® Study Report
12.7. Overcoming barriers to embedding MoV®
12.7.1. We do it anyway
12.7.2. It takes too much time
12.7.3. We can’t afford to make changes
12.7.4. What’s in it for me?
12.7.5. Don’t fix it if it ain’t broke
12.7.6. Fixed returns on capital investment
12.8. Avoiding Failure
12.8.1. OGV - "Common Causes of Project Failure", 2005
12.8.1.1. http://miroslawdabrowski.com/downloads/NAO%20OGC%20-%20Common%20causes%20of%20project%20failure.pdf
12.8.1.2. 1. Lack of clear link between the project and the organisation’s key strategic priorities, including agreed measures of success.
12.8.1.3. 2. Lack of clear senior management and Ministerial ownership and leadership.
12.8.1.4. 3. Lack of effective engagement with stakeholders.
12.8.1.5. 4. Lack of skills and proven approach to project management and risk management.
12.8.1.6. 5. Too little attention to breaking development and implementation into manageable steps.
12.8.1.7. 6. Too little attention to breaking development and implementation into manageable steps.
12.8.1.8. 7. Lack of understanding of and contact with the supply industry at senior levels in the organisation.
12.8.1.9. 8. Lack of effective project team integration between clients, the supplier team and the supply chain.
13. Basic Definitions (according to AXELOS®)
13.1. Portfolios / Programme / Project Management
13.1.1. Portfolio Management
13.1.1.1. A coordinated collection of strategic processes and decisions that together enable the most effective balance of organizational change and business as usual (BAU).
13.1.2. Programme Management
13.1.2.1. The action of carrying out the coordinated organization, direction and implementation of a dossier of projects and transformation activities to achieve outcomes and realize benefits of strategic importance to the business.
13.1.3. Project Management
13.1.3.1. The planning, delegating, monitoring and control of all aspects of the project, and the motivation of those involved, to achieve the project objectives within the expected performance targets for time, cost, quality, scope, benefits and risks.
13.2. Project / Programme / Portfolios
13.2.1. Portfolio
13.2.1.1. An organization’s change portfolio is the totality of its investment (or segment thereof) in the changes required to achieve its strategic objectives.
13.2.2. Programme
13.2.2.1. A programme is a temporary, flexible organization created to coordinate, direct and oversee the implementation of a set of related projects and activities in order to deliver outcomes and benefits related to the organization’s strategic objectives.
13.2.2.2. 3 types of programmes
13.2.2.2.1. Vision-led programme
13.2.2.2.2. Emergent programme
13.2.2.2.3. Compliance programme
13.2.3. Project
13.2.3.1. A temporary organization, usually existing for a much shorter time than a programme, which will deliver one or more outputs in accordance with a specific business case.
13.2.3.2. A particular project may or may not be part of a programme.
13.2.3.3. Whereas programmes deal with outcomes, projects deal with outputs.
13.2.3.4. 5 types of projects
13.2.3.4.1. Compulsory project
13.2.3.4.2. Not-for-profit project
13.2.3.4.3. Evolving (Agile, RUP) project
13.2.3.4.4. Customer/supplier project
13.2.3.4.5. Multi-organization project
13.3. Output, Capability, Outcome, Benefits
13.3.1. Output
13.3.1.1. The deliverable, or output developed by a project from a planned activity. Any project's specialists products. (tangible or intangible)
13.3.1.2. e.g.
13.3.1.2.1. A new just-in-time stock control system
13.3.1.2.2. A new IT system
13.3.1.2.3. Staff training programme
13.3.1.2.4. Revised process
13.3.2. Capability
13.3.2.1. The completed set of project outputs required to deliver an outcome; exists prior to transition.
13.3.2.2. e.g.
13.3.2.2.1. The combination of the outputs ready to ’go live’.
13.3.3. Outcome
13.3.3.1. A new operational state achieved after transition of the capability into live operations. Result of the change derived fron USING the project's outputs.
13.3.3.2. e.g.
13.3.3.2.1. The right materials are available, at the right time, and in the right place
13.3.4. Benefit
13.3.4.1. The MEASURABLE improvement resulting from an OUTCOME perceived as an ADVANTAGE by ONE or MORE of stakeholders, which contributes towards one or more organizational objectives(s).
13.3.4.2. e.g.
13.3.4.2.1. Fewer stock-outs and consequent interruptions to production.
13.3.4.2.2. Reduced obsolescent stock and hence lower write-offs.
13.3.4.2.3. Reduced stock holdings and so less working capital tied up.
13.3.5. Dis-benefit
13.3.5.1. An outcome perceived as NEGATIVE by ONE or MORE stakeholders. Dis-benefits are actual consequences not risks.
14. Interactive MoV® Glossary
14.1. Interactive MoV® Glossary
15. This freeware mind map (aligned with the newest version of MoV®) was carefully hand crafted with passion and love for learning and constant improvement as well for promotion the standard and framework MoV® and as a learning tool for candidates wanting to gain MoV® qualification. (please share and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)
15.1. Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Feel free to visit my website: www.miroslawdabrowski.com
15.1.1. http://www.miroslawdabrowski.com
15.1.2. http://www.linkedin.com/in/miroslawdabrowski
15.1.3. https://www.google.com/+MiroslawDabrowski
15.1.4. https://play.spotify.com/user/miroslawdabrowski/
15.1.5. https://twitter.com/mirodabrowski
15.1.6. miroslaw_dabrowski
16. Watch: Driving Project Management Value with EVM and MoV (interview with David Roberts from CUPE)
17. MoV® Value Management Health Check (1)
17.1. Each health check will occur using the following steps:
17.1.1. Preparation
17.1.2. Data collection
17.1.3. Data analysis
17.1.3.1. Identify trends and patterns, note strengths and deficiencies, identify 3 -5 key themes, conduct intermediate review with the sponsor and identify recommendations.
17.1.4. Review and report
17.1.5. Implementation
18. MoV® Value Management Maturity Model (1)
18.1. Derived from P3M3®
18.1.1. as stated in official publication:
18.1.1.1. "The MoV maturity model mimics the P3M3 structure outlined in Figure D.1."
18.2. 5 Levels of maturity
18.2.1. Level 1 – Awareness process
18.2.2. Level 2 – Repeatable process
18.2.3. Level 3 – Defined process
18.2.4. Level 4 – Managed process
18.2.5. Level 5 – Optimized process
18.3. The use of maturity models is now widespread, with international adoption across multiple industries.
18.3.1. not only Risk Maturity Models
18.3.1.1. Quality
18.3.1.2. Integration
18.3.1.3. Project Managment
18.3.1.4. etc.
18.3.2. see Maturity Models mind map