Comprehensive And Integrated Approach To Project Management And Solution Delivery


Published on

Describes a complete and integrated approach to solution delivery that encompasses project management, project portfolio management, business analysis and solution architecture and design

Effective solution delivery requires an integrated approach to projects across all key disciplines

Project portfolio management
Project management
Business analysis
Solution design

Having silos of expertise that do not communicate or co-operate leads to significant risk

Published in: Technology, Business

Comprehensive And Integrated Approach To Project Management And Solution Delivery

  1. 1. Comprehensive and Integrated Approach to Project Management and Solution Delivery Alan McSweeney
  2. 2. Objectives <ul><li>Describe a complete and integrated approach to solution delivery that encompasses project management, project portfolio management, business analysis and solution architecture and design </li></ul>
  3. 3. Familiar View of Project and Project Portfolio Management <ul><li>Contains the implicit assumption that the solutions being delivered by the projects are designed properly, are implementable and operable and meet business requirements </li></ul><ul><li>Is this correct? Is this the complete picture? </li></ul>Project Portfolio Management Programme and Project Management Prioritising Projects Managing Projects Successfully Project Approvals Project Requests Demand Management Supply Management Strategic Alignment Project Management Methodology Organisation Enablers People Management and Education
  4. 4. Ensuring Strategic Project Alignment to Projects Programmes and projects cascade from business vision to ultimate operation and service delivery Programmes and projects need to be aligned to the overarching business vision and goal Business Vision and Goal Strategy Business Plan Programmes for Strategic Objectives Projects Operation of Solution
  5. 5. Aligning the Solutions Being Delivered <ul><li>Need more than project management </li></ul><ul><ul><li>Not the complete picture </li></ul></ul><ul><ul><li>Cannot treat project management in isolation </li></ul></ul><ul><li>Need to ensure that the solution being managed meets business requirements </li></ul><ul><li>Need to ensure business requirements are captured </li></ul><ul><li>Need to ensure that solutions are designed to deliver business requirements and comply with organisation’s enterprise architecture </li></ul><ul><li>Fundamentally the project exists to manage the delivery of the solution that has been designed to meet business requirements that assist with delivery of the business plan </li></ul>
  6. 6. Complete Picture of Project Selection and Delivery Business Analysis Programme and Project Management Solution Architecture Project Portfolio Management Structured Capture and Management of Requirements Design of Solutions to Meet Requirements Prioritisation of Projects Delivery of Projects
  7. 7. Complete View of Solution Lifecycle and Alignment of Key Project Roles Strategy, Business Planning and Business Analysis Project Management Cycle Solution Delivery - Implementation and Deployment Lifecycle Business Concept Initial Discovery Requirements Elicitation Decision to Proceed Requirements Management and Change Management Operations and Use Initiate Plan Execute and Control Close Setup and Prepare Implement Develop Test Deploy Manage Evolve Solution Architecture and Design Solution Architecture Solution Design Solution Specification and Change Management
  8. 8. Complete Picture of Project Selection and Delivery <ul><li>Need to consider all aspects of project selection and delivery: </li></ul><ul><ul><li>What the business wants (requirements) </li></ul></ul><ul><ul><li>What the business gets (solution that delivers on requirements) </li></ul></ul><ul><ul><li>Delivered according to business priority (project portfolio management) </li></ul></ul><ul><ul><li>Implemented properly (project management) </li></ul></ul><ul><li>Cannot take an individual view without risking problems </li></ul><ul><li>Need to emphasise the importance of the solution whole lifecycle and the interdependence of the roles </li></ul>
  9. 9. The Usual Project Failure Statistics <ul><li>USD$80-USD$145 billion per year is spent on failed and cancelled projects </li></ul><ul><li>Two thirds of all IT projects fail or experience significant problems </li></ul><ul><li>Poorly defined applications have led to a persistent mis-communication between business and IT that contributes to a 66 percent project failure/significant problem rate </li></ul><ul><li>25-40 % of all spending on projects is wasted as a result of re-work </li></ul><ul><li>50 % of projects are rolled back out of production </li></ul><ul><li>60-80 % of project failures can be attributed directly to poor requirements gathering, analysis, and management </li></ul>
  10. 10. Why Projects Fail <ul><li>Very significant Business/IT pain point </li></ul><ul><ul><li>All too frequent implementation of IT solutions that fail to meet business requirements </li></ul></ul><ul><li>Look at the general causes of those failures </li></ul><ul><ul><li>Look for solutions whose implementation will address those causes </li></ul></ul><ul><li>Solutions fail to meet requirements because of some combination of some or all of the following conditions </li></ul><ul><ul><li>Poor understanding of the business need or problem </li></ul></ul><ul><ul><li>Poorly defined requirements </li></ul></ul><ul><ul><li>Inadequately explored solution options </li></ul></ul><ul><ul><li>Poor solution design </li></ul></ul><ul><ul><li>Misalignment between requirements and project scope </li></ul></ul><ul><ul><li>Poor project planning/execution </li></ul></ul><ul><ul><li>Poor change management </li></ul></ul><ul><li>These are all related to an output of a key activity within the overall solution delivery lifecycle </li></ul><ul><li>Cannot separate project management, project portfolio management, business analysis and solution architecture </li></ul>
  11. 11. Business Analysis Approach to Requirements Collection and Management <ul><li>Requirements Management </li></ul><ul><li>Capture – Ensure that the new requirements or change requests are captured </li></ul><ul><li>Assess – Evaluate whether the changes will be actioned and approve or reject </li></ul><ul><li>Change – Undertake the changes </li></ul><ul><li>Requirements Definition </li></ul><ul><li>Gather – Collecting requirements </li></ul><ul><li>Analyse – Analysing, categorising and specifying requirements </li></ul><ul><li>Review – Review and agree exactly what the requirements are </li></ul>Gather Analyse Review Assess Capture Change
  12. 12. Requirements Drive Solution Design <ul><li>Business requirements drive solution design </li></ul><ul><li>Capturing business requirements is essential </li></ul><ul><li>Define key principles/policies/critical success factors for IT </li></ul>Requirements Architecture Design Implementation Business Functional Technical Implementation
  13. 13. Analysis and Design Build Bridge From Business to Solution Problem Requirement Current State Business Analysis and Solution Design Solution Desired Future State Business Analysis: Elicit Requirements Analyse Communicate Validate Solution Design: Translate Requirements into Solution
  14. 14. Requirements Within Solution Lifecycle V Business Requirements Acceptance Test System Requirements System Testing High-Level Design Integration Testing Low-Level Design Component Testing Install and Implement Define Requirements and Solution Deliver Solution and Fulfil Requirements Business Concept Operational Use
  15. 15. Requirements Traceability <ul><li>Provides greater confidence that objectives are being met </li></ul><ul><ul><li>Organising and tracing requirements ensures their incorporation in the design process and makes the basis for design more explicit </li></ul></ul><ul><li>Ability to manage change through impact analysis </li></ul><ul><ul><li>Requirements traceability allows the impact of changes to be assessed more rapidly and effectively </li></ul></ul><ul><li>Improved relationship with the business through better definition and understanding of requirements </li></ul><ul><li>Ability to track progress and status </li></ul><ul><ul><li>Effective requirements management allows measurement </li></ul></ul><ul><li>Save costs through cost / benefit analysis </li></ul><ul><ul><li>Requirements traceability provides a means of defining the relationship between benefits (derived from requirements) and cost (derived from design developed from requirements) </li></ul></ul>
  16. 16. IT Projects to Deliver Business Benefits <ul><li>IT projects should be concerned with adding value to the organisation through selective adoption of new ideas, optimising business processes, and using information technology to achieve a competitive advantage </li></ul><ul><ul><li>Changing rapidly to support new business opportunities </li></ul></ul><ul><ul><li>Driving out wasted time and inefficiency </li></ul></ul><ul><ul><li>Driving out hidden costs </li></ul></ul><ul><ul><li>Avoiding unnecessary complexity </li></ul></ul><ul><li>IT functions are also being transformed to become more service oriented and more closely aligned with the business </li></ul><ul><li>Dual roles of business analysis and solution architect are becoming central to successfully implement and manage IT projects </li></ul>
  17. 17. Centres of Excellence (CoE) <ul><li>Project Management Office functions (PMO) evolved as a PM of CoE to provide a centralized approach to managing projects, in response to the issues associated with complex projects in an environment with low levels of project management maturity and governance </li></ul><ul><li>Business Analysis Centre of Excellence (BACoE) act as the single point of contact for business analysis practices </li></ul><ul><ul><li>Defines the business rules, processes, knowledge, skills and competencies, and tools used by the organisation to perform business analysis throughout the business solution lifecycle, from strategic planning to project initiation to solution delivery and benefits realisation, and finally, solution deactivation </li></ul></ul>
  18. 18. Key Solution Delivery Roles <ul><li>Should not create silos of specialisation </li></ul><ul><ul><li>Project management </li></ul></ul><ul><ul><li>Solution architecture </li></ul></ul><ul><ul><li>Business analysis </li></ul></ul><ul><li>Integrated view will significantly reduce solution delivery risks </li></ul>Project Management Solution Architecture and Design Business Analysis
  19. 19. Solution Architecture Centre of Excellence <ul><li>Solution Architecture Centre of Excellence (SACoE) provides the blueprint for the integration of information and services and the design of individual solutions that comply with overall enterprise architecture </li></ul>Business Architecture Information Architecture Technology Architecture Solution Architecture Overarching Principles, Drivers, Trends, Governance
  20. 20. Enterprise Architecture Components <ul><li>Architecture Governance addresses the governance roles and processes required for maintaining Enterprise Architecture </li></ul><ul><li>Business Architecture provides the high-level representation of the business strategies, intentions, functions, processes, information and assets critical to providing services to the business </li></ul><ul><li>Information Architecture is the compilation of the business requirements of the enterprise, the information, process entities and integration that drive the business and rules for selecting, building and maintaining that information </li></ul><ul><li>Technology Architecture is a disciplined approach to describing the current and future structure and inter-relationships of the enterprise’s technologies in order to maximise value in those technologies </li></ul><ul><li>Solution Architecture is a process within the Enterprise Architecture that focuses on the development and implementation of a solution or service being created for the enterprise </li></ul>
  21. 21. Architecture Blueprint <ul><li>Fully elaborated architectural description of a solution that: </li></ul><ul><ul><li>Provides the basis for detailed design and implementation work </li></ul></ul><ul><ul><li>Assesses project scope and feasibility </li></ul></ul><ul><ul><li>Assures shared understanding of and commitment to solution by all stakeholders </li></ul></ul><ul><ul><li>Integrates solution architecture into project management </li></ul></ul><ul><li>Enable </li></ul><ul><ul><li>Accurate estimation the scope of effort </li></ul></ul><ul><ul><li>Management of (anticipate, avoid, mitigate) risk </li></ul></ul><ul><ul><li>Efficiently and effectively implementation and deployment </li></ul></ul><ul><ul><li>Certainty of common understanding </li></ul></ul>
  22. 22. Integrated Solution Delivery Methodology Advance Integrated Solution Framework Architecture and Realisation Management and Processes Vision and Strategy Architecture Development, Customisation and Configuration Enterprise Management Programme and Portfolio Management Project Management Service Management Architecture Management <ul><ul><li>Implementation and Deployment </li></ul></ul>Operation and Control
  23. 23. Integrated Solution Delivery Methodology <ul><li>Architecture and Realisation </li></ul><ul><ul><li>Concerned with enterprise vision, strategy, architecture, implementation, delivery and subsequent operation </li></ul></ul><ul><li>Management and Processes </li></ul><ul><ul><li>Addresses the management of large-scale business and information technology initiatives and associated programmes and projects </li></ul></ul><ul><li>The phases and processes within the two pillars can be integrated across a programme of work or the services can be delivered independently, depending on the requirements of the organisation </li></ul>
  24. 24. Architecture and Realisation Pillar <ul><li>Vision and Strategy </li></ul><ul><ul><li>Creates the business vision defines the direction for subsequent information technology initiatives. The internal and external requirements and processes are analysed. This allows prioritisation of the business and information system areas that will addressed in subsequent stages. This ensures that all further work is aligned with the vision and strategy </li></ul></ul><ul><li>Architecture </li></ul><ul><ul><li>Designed to translate the Vision and Strategy into an implementable, operable and supportable structure. Architecture can encompass both enterprise and specific solution areas. The scope, requirements and functionality of the business processes and the associated information systems are specified. Architecture is concerned with both business and information technology in parallel. The constituent projects and changes to deliver the architecture are identified </li></ul></ul><ul><li>Development, Customisation and Configuration </li></ul><ul><ul><li>Selects, designs, builds, customises and tests the elements of the solution. This can include some or all of customised development, package customisation and system enhancement. The development activities related to business change and technical infrastructure are addressed </li></ul></ul><ul><li>Implementation and Deployment </li></ul><ul><ul><li>Takes the solution components and creates a fully operable system, complete with data and business process changes. This stage includes integration testing, pilot, data conversion documented procedures, training, and operational readiness and acceptance </li></ul></ul><ul><li>Operation and Control </li></ul><ul><ul><li>Creates and implements practices for ensuring defined service levels for the operation, maintenance, and support of the new or modified systems </li></ul></ul>
  25. 25. Management and Processes Pillar <ul><li>Enterprise Management </li></ul><ul><ul><li>Involves establishing business objectives, monitoring achievement against targets and making necessary corrections </li></ul></ul><ul><li>Programme and Portfolio Management </li></ul><ul><ul><li>Directs and manages programmes and portfolios of initiatives and undertakings offerings to balance benefits, costs, resources and risks in a strategic context and ensuring benefits realisation. System Dynamics can establish the competency within an organisation to provide this service internally </li></ul></ul><ul><li>Project Management </li></ul><ul><ul><li>Concentrates on the effective and efficient processes required to identify, coordinate, and continuously focus people and resources on achieving project objectives and commitment within time, cost, resource and quality controls. This enables organisations to deliver both the simple and complex initiatives and to perform projects capably </li></ul></ul><ul><li>Service Management </li></ul><ul><ul><li>Controls and manages the operational services phases of the overall initiative life cycle. Service request management handles requests from users. It manages their fulfilment and includes logging, performing initial analysis, monitoring, prioritising, measuring, and closing. Service delivery management directs and manages services to ensure that the end-user receives the agreed service </li></ul></ul><ul><li>Architecture Management </li></ul><ul><ul><li>Concerned with the business, technical, and operational procedures and processes needed to ensure and maintain integrated enterprise and solution architecture during the implementation of the solution and its subsequent operation </li></ul></ul>
  26. 26. Summary <ul><li>Effective solution delivery requires an integrated approach to projects across all key disciplines </li></ul><ul><ul><li>Project portfolio management </li></ul></ul><ul><ul><li>Project management </li></ul></ul><ul><ul><li>Business analysis </li></ul></ul><ul><ul><li>Solution design </li></ul></ul><ul><li>Having silos of expertise that do not communicate or co-operate leads to significant risk </li></ul>
  27. 27. More Information <ul><ul><ul><li>Alan McSweeney </li></ul></ul></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul>