• Investigating the situation
1. Study PID for understanding the background and the situation. (summarise information with rich pictures, mind maps, spaghetti maps, fishbone diagrams)2. Appropriate the situation by carrying out investigation with key stakeholders (investigation qualitative/quantitative techniques: interviewing, workshop, observation / document analysis, questionnaires, sampling.)
• Considering the perspectives
1. Identify key stakeholders with a RASCI, understand their business perspectives by interviewing them and analyse their positions thanks to a stakeholder power/influence analysis and a CATWOE.2. Elaborate conceptual models of each business perspective, communicate/manage these stakeholders' views in workshops for building an unique or consensual conceptual business perspective that could be traduced into a common desired business system.
• Analysing the needs
1. Analyse activities of the "as-is" business activity model (BAM) by using activity analysis techniques like activity sampling.2. Develop the "to-be" business model and establish a gap analysis for considering business needs.
• Evaluating the options
1. Consider business options and short-list the most feasible in terms of business, technical, financial aspects by using impact/risk/cost-analysis analysis.2. Develop the business case that details each of these chosen options and give recommendations.
• Defining the requirements
1. Elicit and validate requirements for the "to-be" business model by taking an holistic approach and by considering tacit information.2. Document them in catalogue of requirements (MOSCOW of functional/non-functional, technical and general requirements) and model the IT system with UML and entity-relationship models.
• Delivering changes
1. Chose the project lifecycle according to methods/standards chosen/possible with SLDC and business strategy/approach to implement changes.2. Plan the final implementation the new IT system and take in account each aspects of underlying changes in terms of Skills, Staff, Style, Structure, Strategy and Values . (McKinsey model).
3. Review predicted tangible/intangible benefits presented in the business case during the project's decisions gates.
No comments:
Post a Comment