Downloaded 12 times
Uploaded byAmazee Labs
Strategy Session (DrupalCamp CO)
The document discusses solution architecture as a strategic approach for successful project development, emphasizing the importance of defining measurable goals and addressing hidden obstacles. It outlines the roles, processes, and documentation involved in creating effective information systems or applications, while also highlighting essential elements such as truth, reality, and leadership clarity. Example goals are presented to illustrate strategy effectiveness, alongside common pitfalls and recommendations for successful project execution.
More Related Content
Similar to Strategy Session (DrupalCamp CO)
Strategy Session (DrupalCamp CO)
- 1. Solution Architecture: designing astrategy for project success DrupalCamp Colorado: August 2nd, 2014
- 2. Diana Montalion Dupuis DianaMontalionDupuisMichaelSchmid CEO Amazee Labs (Austin) amazeelabs.com @dianadupuis Follow me on Twitter and I’ll follow you back!
- 3.
- 4.
- 5. Strategy is … •Intuition • Wisdom and experience • Logic and common sense • Art and poetry • When applied to application development, an engineering process (constantly reinvented) sometimes called solution architecture
- 6. According to Wikipedia “Solutionarchitecture (within or without enterprise architecture) is a combination of role, process and documentation that is intended to address specific problems and requirements, usually through the design of specific information systems or applications. ! The term solution architecture can be used to mean either or both: * Documentation describing the structure and behavior of a solution to a problem, or * A process for describing a solution and the work to deliver it.”
- 7. According to Wikipedia “Solutionarchitects typically produce solution outlines and migration paths that show the evolution of a system from baseline state to target state.” http://thewellwrittenwoman.com/wp-content/uploads/2012/12/sigh.png
- 8. According to me Solutionarchitecture attempts to define an ecosystem that will organically produce the stated, measurable goals. the goals, not the solution
- 9.
- 10. Key elements • Truthand reality (aka bullshit detector) • Measurable goals, prioritized • Overcome hidden obstacles implicitly • A construct (the architecture itself) in the form of a document
- 11.
- 12. Things to lookfor … • Ripping the fabric of space time • Hidden complexity • Too much or too little control • No goals or features don’t match goals • Leadership confusion (can focus on what but not how) • Truthiness: reality refuses to bow down to power
- 13.
- 14. What to giveback • Truth • Insights • Facts • Options
- 15. What not togive back • Snark • False hope
- 16.
- 18. Measurable goals • Reducecalls to customer service by 25% in 3 months • Increase subscription to the newsletter by 150% in 6 months • Increase page view time from 3 seconds to 10 seconds on newly published content • Increase traffic by 30% in 6 months (how does the application do that?)
- 19. Hidden obstacles • Theyare *always* there • A good strategy overcomes them • ALES
- 20. ALES • Ask • Listen •Empathize • Strategize
- 21. Hidden examples • The“real” goal is something different from the stated goal and/or two (or more) stakeholders disagree • The last six vendors “didn’t work out” • The “final say” comes from a boss who delegates but doesn’t or a person with no tech experience is “in charge” of the project but isn’t • There’s a lot of focus on low priority details
- 22. Construct • Overview: businessreasons to do the project and clear, measurable goals • The vision with just enough detail to be flexible (the art part) • Drupal domains • Estimation • Include assumptions
- 23. Drupal domains • Coreand DevOps • Design • Basic, responsive theme • Data architecture and migration • Art and architecture: the features and/or however your concept is described • Testing • Project management
- 24. Examples • Dual organizationsand data • This site is totaled • Traditional “by the sections” • Building the site • Feature phases, like buying a car
- 25. When off track •Let go of the original plan • Prioritize against goals • Create buckets and phases • Retrospect, include everyone • Define the now known unknowns and include them
- 26.