Starting Perspective: Product Planning

WG 02

Our ‘Context’ for Defining Proficiency

• Necessary Elements for Proficiency– Iteration and release plans– Architecture board– Road Map for releases

• Value of the investment is moderated by the type of the organization

What does it mean for an organization to be proficient at architecture-centric practices?

• The effort that you put into architecture is dependent on the value of the architecture to the organization

What are the linchpins for being proficient at architecture-centric development?

• Architect must maintain and communicate a clear vision of the software architecture

What are the key indicators of organizational proficiency or lack of proficiency?

• Do you have a vision or roadmap of your product and/or architecture against which to evaluate your architecture for the needs that it enables or constrains?

• Do your architects have the seniority to be involved in the strategic direction of the organization?