4. What?
– Architecture Design Sessions (ADS). A
two or three day envisioning workshop
with key business and technology
stakeholders.
– Proof of Concept (POC). A two or three
week workshop to construct, integrate
and/or validate the concepts from the
ADS.
5. Who participates?
– Microsoft Services
– architects and subject matter experts
– Customer
– business and technology stakeholders
– Partner
– technology experts and system analysts
6. Goals
– take time-out from the day-to-day job and
look at the big picture
– consider 'how things might be‘
– understand the problem and how to solve
it
– make decisions
7. How consultants help?
– Share knowledge on relevant technology
– Remove uncertainty, help to develop the
plan
– How much will this cost?
– How can I train my staff?
– What have others done?
– Give something in writing
8. ADS non-goals
– Designing the full solution in detail
– Getting you to come back for a POC
– Selling anything
9. ADS process
– Discovery
– the customer describes their business and context
– participants agree on ADS goals
– Envisioning
– extract 'proof scenarios' that can be described and built
(these are usually thin slices, rather than breadth)
– consider the technology and approach for those scenarios
(analyze existing technology, integration points and other
risks and constraints)
– Planning
– detailed planning around 'who, when and what'
15. Why ADS/POC?
– Acceleration:
– thought leadership
– technical proof
– assisting with budgets
– De-risking:
– focus on the hardest bits of a concept
– prove that approach is well undestood
– remove risks from the larger project
– Evaluation
– assess the technologies being used
– consider the impact of those in a way that may not be
possible to achieve internally (because of the risk)
