Key Takeaways Trust and transparency provide the foundation for effective conversations. You won’t be successful until you can have open and meaningful conversations with business stakeholders. Frame scope discussion in terms of business outcomes, not features. Features may or may not deliver desired outcomes and may come and go, but outcomes are relatively stable and tend to be refined but not completely invalidated. Every conversation with a business stakeholder will probably turn into a conversation about money. And what they are most concerned about is not absolute cost, but cost-effectiveness. Cost thresholds can help teams make better architectural decisions. Understanding the cost threshold of an outcome helps the IT team make choices that can improve profitability without compromising the outcomes the solution delivers. An application is like an iceberg: business stakeholders only see features "above the water", so most of the development team’s architectural decisions are invisible and "underwater". Discuss architectural decisions in terms of customer experience to help stakeholders understand the trade-offs between different alternatives. Quality Attributes can help to frame this discussion by helping you to talk about the quality of the customer’s experience in concrete and measurable ways. "Almost every problem in software development is fundamentally […]
K&X Design and Investment Technology, LLC
Invest The Invisible Impact
K&X Design and Investment Technology, LLC
Invest The Invisible Impact
