Nashreen Hofmeester<br />12 September 2009<br />EA Project Management<br />Programme<br />understanding  risk and managing...
Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> ...
Definitions<br />Programme<br />‘A group of related projects managed in a co-ordinated way to obtain benefits and control ...
Project vs. Programme<br />Programme<br />Project<br /><ul><li>Narrow scope , specific deliverables, time-frame, budget.
Success measured by budget, on-time , outcome delivered according to scope.
Minimise scope variation.
Detailed project plan.
Focused on delivery.
Wide scope; may have to change over time.
 Success measured by benefits delivered, new capabilities established, etc.
High-level plan providing guidance to projects.
Co-ordinated management across portfolio’s.</li></li></ul><li>EA as programme<br />Ongoing iterative effort:<br />Plan, de...
Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> ...
Understanding your stakeholders<br />‘An individual or group with an interest in the success of an organization in deliver...
Categories of stakeholders<br />Source: TOGAF 9TM, 2009<br />
Sample Stakeholder Category Interests<br />Source: pp 286-292, TOGAF 9TM, 2009<br />
Stakeholder analysis<br />Identify and classify stakeholders<br /><ul><li>Identify people and groups with interest in the ...
Identify who will be impacted by current iteration
Review and verify stakeholders and their concerns
Select appropriate views and viewpoints</li></ul>Confirm <br />Stakeholder <br />concerns<br />Identify <br />concerns<br ...
Create stakeholder matrix
Determine management approach</li></li></ul><li>Sample stakeholder matrix<br />
Sample stakeholder power grid<br />
Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> ...
Common challenges and issues<br />Poor executive buy-in<br />Un-cooperative business owners<br />Analysis ‘fatigue’<br />B...
Common challenges and issues<br />No clearly defined objectives for EA<br />No up-front success metrics<br />Lack of ‘shar...
Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> ...
What is risk<br />‘The possibility of incurring misfortune or loss’<br />Collins Dictionary<br />‘..the project risks are ...
Nature of risk<br />Inherent:<br />Nature of project objectives or scope<br />Acquired:<br />Results from selected organis...
Risk management process<br />Identify and define risks<br /><ul><li>Use collaborative approach
Identify overall risks for project
Revisit at start of each new phase
Maintain risk register
Assign ownership
Upcoming SlideShare
Loading in …5
×

Enterprise Architecture Program Management Challenges

1,793 views

Published on

Presented at the 2009 South African Government GITO Council Techni-Click.

Published in: Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,793
On SlideShare
0
From Embeds
0
Number of Embeds
37
Actions
Shares
0
Downloads
135
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Enterprise Architecture Program Management Challenges

  1. 1. Nashreen Hofmeester<br />12 September 2009<br />EA Project Management<br />Programme<br />understanding risk and managing failure<br />
  2. 2. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  3. 3. Definitions<br />Programme<br />‘A group of related projects managed in a co-ordinated way to obtain benefits and control not available from managing them individually.’<br />Project Management Institute (PMI) <br />Project<br />‘A project is a unique process consisting of a set of co-ordinated and controlled activities with start and finish dates, undertaken to achieve an objective conforming to specific requirements including the constraints of time, cost and resources.’<br />International Organisation for Standards (ISO)<br />
  4. 4. Project vs. Programme<br />Programme<br />Project<br /><ul><li>Narrow scope , specific deliverables, time-frame, budget.
  5. 5. Success measured by budget, on-time , outcome delivered according to scope.
  6. 6. Minimise scope variation.
  7. 7. Detailed project plan.
  8. 8. Focused on delivery.
  9. 9. Wide scope; may have to change over time.
  10. 10. Success measured by benefits delivered, new capabilities established, etc.
  11. 11. High-level plan providing guidance to projects.
  12. 12. Co-ordinated management across portfolio’s.</li></li></ul><li>EA as programme<br />Ongoing iterative effort:<br />Plan, develop, realise, maintain<br />Top-down planning of architecture projects<br />Balanced and consistent manner<br />Facilitate alignment to enterprise strategy<br />Facilitate compliance management<br />Manage interdependencies between enterprise projects<br />
  13. 13. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  14. 14. Understanding your stakeholders<br />‘An individual or group with an interest in the success of an organization in delivering intended results and maintaining the viability of the organizations products and services.’<br />Balanced Scorecard Organization.<br />Why<br />Identify people and groups with interest<br />Know who you are dealing with<br />Who decides, who gains / lose, who controls resources, who influence,?<br />Identify their concerns<br />Focus your effort<br />Produce ‘fit-for-purpose’ architecture<br />
  15. 15. Categories of stakeholders<br />Source: TOGAF 9TM, 2009<br />
  16. 16. Sample Stakeholder Category Interests<br />Source: pp 286-292, TOGAF 9TM, 2009<br />
  17. 17. Stakeholder analysis<br />Identify and classify stakeholders<br /><ul><li>Identify people and groups with interest in the EA programme
  18. 18. Identify who will be impacted by current iteration
  19. 19. Review and verify stakeholders and their concerns
  20. 20. Select appropriate views and viewpoints</li></ul>Confirm <br />Stakeholder <br />concerns<br />Identify <br />concerns<br />Map<br />stakeholders<br />Tailor views<br />and viewpoints<br /><ul><li>Understand concerns and issues per stakeholder
  21. 21. Create stakeholder matrix
  22. 22. Determine management approach</li></li></ul><li>Sample stakeholder matrix<br />
  23. 23. Sample stakeholder power grid<br />
  24. 24. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  25. 25. Common challenges and issues<br />Poor executive buy-in<br />Un-cooperative business owners<br />Analysis ‘fatigue’<br />Business uncertainty (change, etc.)<br />Mal-aligned expectations<br />Lack of governance practice<br />Operations focus vs. Strategic focus<br />
  26. 26. Common challenges and issues<br />No clearly defined objectives for EA<br />No up-front success metrics<br />Lack of ‘shared reality’ between business and ICT organisation<br />Lack of project / programme management and practice<br />Lack of skills or immature EA skills<br />Historical ‘baggage’<br />Unsuccessful previous attempts<br />
  27. 27. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  28. 28. What is risk<br />‘The possibility of incurring misfortune or loss’<br />Collins Dictionary<br />‘..the project risks are events or uncertain conditions that, in case they happen, they provoke a positive or negative effect in the project objectives.’<br />Project Management Body of Knowledge (PMBoK)<br />
  29. 29. Nature of risk<br />Inherent:<br />Nature of project objectives or scope<br />Acquired:<br />Results from selected organisation, approach / technology<br />Contextual:<br />Results from events, circumstances outside project<br />
  30. 30. Risk management process<br />Identify and define risks<br /><ul><li>Use collaborative approach
  31. 31. Identify overall risks for project
  32. 32. Revisit at start of each new phase
  33. 33. Maintain risk register
  34. 34. Assign ownership
  35. 35. Monitor and manage
  36. 36. Prioritise according to impact
  37. 37. Assess in terms of level of acceptability</li></ul>Define,<br />implement<br />response<br />Evaluate<br />risks<br />Analyse<br />risks<br />Monitor and<br />manage<br /><ul><li>Determine cause
  38. 38. Estimate probability
  39. 39. Estimate consequence
  40. 40. Define formal risk reporting mechanism
  41. 41. Formulate response to decrease, contain and control</li></li></ul><li>Common risks encountered<br />Lack of organisational readiness<br />Lack of EA capability maturity<br />Failure in scope definition and management<br />Failure in governance<br />Failure in schedule<br />Failure in risk management<br />Failure in communications management<br />Resource constraints<br />Political change<br />
  42. 42. Effective risk management<br />Commitment at all levels<br />Communication and consultation<br />Effective project management<br />Risk ownership<br />Partnership approach<br />Continuous risk management (mitigating)<br />
  43. 43. Mapping Risk<br />
  44. 44. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  45. 45. Architectural artefact vs. deliverable<br />Artefact:<br />More granular work product<br />Describes architecture from specific viewpoint<br />Catalogues<br />Matrices<br />Diagrams<br />Deliverable:<br />Contractually specified work product<br />Formally reviewed, agreed to and signed off<br />Snapshot of architecture landscape<br />Source: TOGAF 9TM, 2009<br />
  46. 46. TOGAF 9TM deliverables<br />
  47. 47. GWEA V1.2 deliverables<br />
  48. 48. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common Challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  49. 49. TOGAFTM ADM and project management<br /><ul><li>Conduct ADM cycles within project management framework of enterprise.
  50. 50. Frame implementation and migration plan within enterprise project delivery methodology</li></ul>Source: TOGAF 9TM, 2009<br />
  51. 51. Project management methodologies<br />Prince2<br />
  52. 52. Project management methodologies<br />PMBoK<br />
  53. 53. ADM and project management phases<br />
  54. 54. Agenda<br />1<br /> Project management vs. Programme management<br />2<br /> Understanding your stakeholders<br />3<br /> Common Challenges and issues<br />4<br /> Managing risk<br />5<br /> EA project deliverables<br />6<br /> TOGAFTM ADM and project management<br />7<br /> Conclusion<br />
  55. 55. Successful EA programmes<br />
  56. 56. ?<br />?<br />?<br />Questions<br />

×