How-agile-teams-can-pursue-technical-excellence: Difference between revisions

Article published by McKinsey and reviewed by Nikolay Sidelnikov
(Created page with "{{#seo: |title=Review by B2B Experts |title_mode=append |keywords= architecture, platform |description= The article by McKinsey explains why adopting a well-architected framework helps organizations meet the increasing expectations around technical excellence that accompany the transition to the modern cloud environment. |image=Uploaded_file.png |image_alt=Wiki Logo }} {{Infobox article | source = https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/tech-...")
 
 
Line 21: Line 21:
== Abstract ==
== Abstract ==


The article "How agile teams can pursue technical excellence" explains why non-functional requirements are so important and suggests the idea of a "well-architected framework" based on five pillars:  
The article "How agile teams can pursue technical excellence" brings a usefull advice on selection of software being oriented for high business performance due technical excellence.
 
Authors explain why non-functional requirements are so important for business and suggest the idea of a "well-architected framework" based on five pillars:  


* '''Operational excellence''': run and monitor systems to provide business value while continually improving support processes and procedures
* '''Operational excellence''': run and monitor systems to provide business value while continually improving support processes and procedures
Line 31: Line 33:
All these pillars are explained in more details in the article.
All these pillars are explained in more details in the article.


They highlighted, that ''cost optimization'' is often the most neglected pillar, though it is critical in today’s pay-as-you-go cloud-deployment model.
McKinsey highlighted, that ''cost optimization'' is often the most neglected pillar, though it is critical in today’s pay-as-you-go cloud-deployment model.


A quote:
A quote:

Latest revision as of 10:02, 1 February 2024

How agile teams can pursue technical excellence (with abstract)
Published ByArticles by McKinsey
Publish Date2022
AuthorsJeanine Murphy, Michael Sioufas
Topics Tech for business
Statistics
Article Sizewords
DiagramsNo
Downloadable VersionNo
Reviewers
Page OwnerNikolay Sidelnikov
Summary AuthorNikolay Sidelnikov


Abstract

The article "How agile teams can pursue technical excellence" brings a usefull advice on selection of software being oriented for high business performance due technical excellence.

Authors explain why non-functional requirements are so important for business and suggest the idea of a "well-architected framework" based on five pillars:

  • Operational excellence: run and monitor systems to provide business value while continually improving support processes and procedures
  • Security: protect information, systems, and assets while delivering business value through risk assessments and mitigation strategies
  • Reliability: ensure systems can recover from infrastructure or service disruptions, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues
  • Performance efficiency: use resources efficiently to meet system requirements and to maintain performance as demand changes and technologies evolve
  • Cost optimization: run systems that provide business value at the lowest price point by minimizing or avoiding unnecessary costs

All these pillars are explained in more details in the article.

McKinsey highlighted, that cost optimization is often the most neglected pillar, though it is critical in today’s pay-as-you-go cloud-deployment model.

A quote:

Teams that use the well-architected framework to improve NFRs and overall technical excellence can begin by asking specific questions to align their focus with each of the five pillars:

  • Is the application designed to use resources in the most cost-effective way?
  • Have the necessary security controls been implemented to ensure the integrity of the application’s data and to detect and address security events?
  • Are we taking measures to meet the reliability and performance expectations of our user community?