Skip to main content

Understanding Our Approach: Rooted in Lean and Agile Principles and Practices

At Avesta Technologies, our methodology for product development and, by extension, our approach to engineering metrics, is deeply rooted in the principles of Extreme Programming (XP) and Continuous Delivery (CD). We believe these frameworks, championed by industry visionaries, provide the most effective path to building high-quality software sustainably and responsively.

This philosophy directly shapes how Avesta Technologies selects, interprets, and acts upon engineering metrics when working with its clients.

Core Tenets: XP and CD​

  • Extreme Programming (XP): We embrace XP's values—Simplicity, Communication, Feedback, Courage, and Respect—and its core practices. This means:

    • Short Feedback Loops: Metrics are a crucial component of our feedback mechanisms, allowing us to inspect and adapt rapidly.
    • Continuous Improvement (Kaizen): XP is built on the idea of relentless improvement. Metrics help us identify areas where we can refine our processes and practices.
    • Collective Ownership & Collaboration: We view metrics as a shared tool for the entire team (Avesta Technologies and the client) to understand and improve collective performance.
    • Sustainable Pace: Metrics can help us ensure the development team is working effectively without being overburdened, leading to higher quality and better long-term productivity.

  • Continuous Delivery (CD): The ability to get changes of all types—new features, configuration changes, bug fixes, and experiments—into production, or into the hands of users, safely and quickly in a sustainable way is paramount. CD practices influence our metrics by emphasizing:

    • Speed and Efficiency: Metrics like Lead Time and Cycle Time are direct indicators of CD capabilities.
    • Stability and Quality: Metrics such as Change Failure Rate and Mean Time to Recovery (MTTR) are critical for ensuring that speed doesn't come at the cost of stability.
    • Automation: CD relies heavily on automation. While not always directly measured as a standalone metric in this playbook, the effectiveness of automation (e.g., test automation, deployment pipelines) underpins many of the metrics tracked.

Inspired by Thought Leaders​

Our approach is continuously informed by the wisdom of renowned figures in software development and product management:

  • Kent Beck: The creator of Extreme Programming, whose emphasis on values, principles, and practices provides the foundation for our agile development.
  • Dave Farley: A pioneer in Continuous Delivery, his work (e.g., "Continuous Delivery," "Modern Software Engineering") reinforces the importance of speed, stability, and scientific thinking in software development.
  • Martin Fowler: His insights into software design, architecture, refactoring, and agile methodologies guide our technical practices and our understanding of how to build evolvable systems.
  • Robert C. Martin (Uncle Bob): A proponent of Clean Code, Clean Architecture, and software craftsmanship, his principles guide our commitment to high-quality, maintainable codebases.
  • Marty Cagan: His work on product leadership (e.g., "Inspired," "Empowered") reminds us that engineering efforts must ultimately serve to deliver value to users and the business, a key consideration when selecting and interpreting product-impact metrics.

Metrics as Tools for Growth​

For Avesta Technologies and its clients, engineering metrics are not instruments of judgment. They are tools for:

  • Facilitating Constructive Conversations: Providing objective data points to discuss what's working well and where opportunities for improvement lie.
  • Identifying System Bottlenecks: Helping us see constraints within the development and delivery system, not just within individual performance.
  • Driving Data-Informed Decisions: Guiding choices about process changes, technology adoption, and resource allocation.
  • Fostering a Culture of Learning and Psychological Safety: Encouraging experimentation and viewing deviations in metrics as learning opportunities in a safe environment.

By understanding these foundational principles, we can ensure that the use of metrics is always aligned with the shared goal: to build better software, faster and more reliably, for our clients.