Harnessing Stakeholder Needs To Envision, Validate and Evolve a Solution…

1. Harnessing Stakeholder NeedsTo Envision, Validate and Evolve a Solution… Erol Eraybar Sr. Consultant eeraybar@columbus.rr.com

2. Can an Architect Harness Stakeholder Needs? Learn how in ten (10) minutes or less! • Process-Centric, Scenario-Driven Modeling • Strategic Design and Tactical Implementation • Visual Communication Techniques and Tools

3. Who are your “Stakeholders”? • Discover Your Stakeholder’s to Uncover Needs • Holistic Stakeholder Identification • Internal and cross-boundary • External to the organization • Government Agencies • The Customer

4. What are Stakeholder “Needs”? • Needs take many forms • Musts • Wants • Expectations

5. Stakeholder Needs May Get Away • Captured and Harnessed • Managed and Controlled • Satisfied or Exceeded

6. Use Process-Centric, Scenario-Driven Techniques • Mantra for approaching all facets of the SDLC • Customer-centric mindset • Processes drive requirements • No processes = No requirements = Nothing to build

7. Design Strategically to Implement Tactically • Realistic to harness (all) needs at inception? • Foresee all architectural underpinnings? • Will stakeholders become overwhelmed? • Business Users / Customers • IT • Impact of unrealized business strategy while building the perfect solution?

8. How to Develop a Strategic / Tactical Mindset • Devise a phased, incremental approach • Embrace technical simplicity • Rapid delivery of out-of-the-box (OOTB) capabilities and/or core functionality • Socialize the new solution as a launch pad • Continuous improvement • Track record of success

9. Use Visual Communication to Validate & Evolve • Visual Diagrams and Pictorial Graphics • Facilitate conceptualization and validation • Real-Time and After-the-Fact Artifacts • Process Diagrams • Architecture Diagrams • Mind Maps Telegraph Machine

10. Process Diagrams – Scenario Driven One Stakeholder Type / Swimlane Process Step

11. Architecture Diagrams – Strategic Design Strategy to Scale Stakeholder Groups

12. Mind Maps – Visual Harnessing of Needs Collapsing Detail for “Birds-Eye View” Expanding Detail for “Worms-Eye View” Thought Fragment – Item needs to be fleshed-out

13. An Architect Can Harness Stakeholder Needs! • Needs are best captured, refined, and validated in a process model context • Deploy the solution in stages to demonstrate the technology performs as promised • Collaboration can be significantly improved through visual communication techniques

14. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.