Business Case and Architecture

2,022 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,022
On SlideShare
0
From Embeds
0
Number of Embeds
590
Actions
Shares
0
Downloads
28
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Business Case and Architecture

  1. 1. Business caseand architecture<br />Alistair Herriott – BearingPoint<br />January 18th 2011<br />
  2. 2. Trusted advisor to enable the business<br />Source : Book Architecture Process<br />
  3. 3. Architects designing solution from requirements<br />Requirements<br />Architecture<br />Development<br />Define<br />Requirements<br />Create Logical Architecture<br />Create Logical Detailed Design<br />Create Physical<br />Architecture<br />Create Physical Detailed Design<br />Source : Book Architecture Process<br />
  4. 4. Industry Business Process as a starting point<br />Source : TeleMangement Forum<br />
  5. 5. Capturing benefits of requirements with User Stories<br />Vision Stories<br />Customer Experience Stories<br />Solution Stories<br />Component Stories<br />
  6. 6. Problem Statement <br />
  7. 7. Document the pain points and improvement areas<br />End to end process to automate<br />.<br />…<br />Step N<br />Step 1<br />Step 2<br />Step 3<br />Step 4<br />Pain Points<br />Improvement Areas<br /><ul><li>Document the pain points that are happening in the business. This is very descriptive.
  8. 8. Document suggestions that people have identified at meetings and discussions.
  9. 9. This demonstrates that you are listening.</li></li></ul><li>Capturing benefits of requirements with User Stories<br />Vision Stories<br />Customer Experience Stories<br />Solution Stories<br />Component Stories<br />
  10. 10. User Story Template<br />9<br />
  11. 11. Calculating the effort required to complete process<br />
  12. 12. Measures, Inputs and Outputs<br />
  13. 13. Roadmap for the Business<br />Q1 2011<br />Q2 2011<br />Q3 2011<br />Q4 2011<br />Customer<br />Products<br />1<br />2<br />3<br />4<br />5<br />6<br />7<br />8<br />9<br />10<br />11<br />12<br />Integrate<br />Change<br />Enhance<br />Full integration<br />Configuration<br />Configuration<br />Deploy <br />Targeting<br />Preparation<br />Deploy<br />Migration<br />Listen<br />Operate<br />Full solution<br />Engage<br />Enhanced<br />Capability<br />Release<br />ABC<br /><ul><li>A
  14. 14. B
  15. 15. C</li></ul>ABC<br /><ul><li>A
  16. 16. B
  17. 17. C</li></ul>ABC<br /><ul><li> A
  18. 18. B
  19. 19. C</li></ul>ABC<br /><ul><li> A
  20. 20. B
  21. 21. C</li></ul>Capability<br />Descriptions<br />
  22. 22. Project Plan for the business case development<br />Week 1<br />Week 2<br />Week 3<br />Week 4<br />Week 5<br />Week 6<br />Interview business owners<br /><ul><li>xx
  23. 23. xx
  24. 24. xx
  25. 25. xx
  26. 26. xx</li></ul>Gather key business scenarios<br /><ul><li>xx</li></ul>Document User Experience Stories<br />Map business scenarios/CE stories<br />Step N<br />Team Meeting<br />Steering Committee<br />
  27. 27. Contact check list for validating the figures<br />
  28. 28. Influencing and informing the stakeholders<br />Source : Book Architecture Process<br />
  29. 29. Thank you<br />alistair.herriott@bearingpointconsulting.com<br />Alistair Herriott<br />

×