Skip to main content

The Shape of Your Portfolio

Jann Thomas
Reading: The Shape of Your Portfolio

What is your capability model showing you?

In the world of Agile Software development, capability model may not be a term commonly used. We often think of Agile as describing how the development teams function, standups, planning, demo, retro, much of the delivery world moves to the scrum rhythm. Capability model, now how does that fit into building better software?

A capability model is a graphical definition of what your organization does. In the most simplistic form, the model is an outline of business processes. Once the outline is created, the components of the outline can be assessed as to how they are valued and how they are performing for the business. Normally a portfolio team responsible for a line of business will assess the capabilities within their line of business. All of this analysis is just a pre-cursor to portfolio planning that will allow an organization to determine where should we invest in tools to support our business processes. The tool used to improve the performance of a business capability we are going to discuss is software.

So how do you get your capability model to help you decide where to focus your software dollars? And what does that focus tell you about your current portfolio? Lets look at how a Value/Performance matrix and Suitability/Pace of Change Matrix can facilitate the answers to the questions.

In the case of the capability analysis below the organization has defined their portfolio, as needed major improvements to Architecture. This portfolio team agrees that to grow or exploit business capabilities the underlying software architecture needs a major improvement. The shape of the portfolio is helping to communicate where there will not be an influx of new features but that new tools and software will improve capabilities.

Capability 1

For a similar business capability Model but Architecture that can support new features the Architectural Model below helps to communicate that most of the investment will result in new features and may have an impact on organizations other than Software.

Capability 2

In a mature architecture, that is well suited and aligned to business priorities, most of the change in the system will be defined as small enhancements. This allows the rest of the organization to consume change in small chunks so investments in training should be minimal.

Capability 3

Portfolio planning helps the organization to align software delivery to business priorities and predict the impact of software changes. The capability model combined with software architectural matrix is a valuable communication tool.

Next How To Tell What Is Actually Going On At The Portfolio Level

Jann Thomas is a 20-year veteran of the software industry.  She has worked as a developer, team lead and development manager leading teams to deliver great software.

Comments (3)

  1. Alex Randell
    Reply

    Great blog – thank you so much for making the connection between business capabilities, portfolio health, and agile efforts. There is so much value in this and it is something both the business architecture and agile communities should understand and continue to drive forward.

    A couple of minor points from the business architecture angle (I am practitioner of this discipline):

    From a technical/literal standpoint, it should be a capability map, not model. And a capability map depicts “what a business does”, not a process. A process depicts how a business accomplishes that “what” (roughly speaking).

    I’d be glad to discuss this more with you, if you are interested! Thanks again!

    Reply
    • Jann Thomas
      Reply

      Alex thanks for reading and thanks for the comment. When defining the concepts here it is important to use consistent terminology. I appreciate your feedback. I will drop you a mail and we can continue the conversation.

      Thanks,
      Jann

      Reply
  2. marco
    Reply

    What do the various colours refer to?

    Reply

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

What is the Worth of a Good Product Owner? w/ Tim Wise

This week, on SoundNotes, we’re featuring another question from a student in one of our Certified Scrum classes. The question came from someone who’s working in an organization that doesn’t see value in the role of Product Owner and isn’t convinced that it’s needed as part of the Scrum Team. The question: What is the […]

How Do I Use Scrum on Data Warehouse Projects? w/ Dave Nicolette

In one of my recent Certified Scrum Master classes, I had a number of students who were working on projects involving migrating from a legacy data warehouse to new data warehouses. Figuring out how to apply Scrum to the work they were doing presented a number of challenges and left some open questions.  Here are […]

Maximizing the Amount of Work Not Done

One of the principles of the Agile Manifesto reads: “Simplicity – the art of maximizing the amount of work not done – is essential.” Okay. What does that mean? Does it mean we should avoid doing our work to the extent possible? Well, not exactly. Consistency Between Lean and Agile Principles Without coming at the […]

Prioritizing the Work to Maximize Return w/ Dennis Stevens

This week, on SoundNotes, we’ve got Part 3 of a trio of interviews with LeadingAgile Chief Methodologist and Co-Founder Dennis Stevens. The series focuses on how to build an organization that can embrace change. In the final episode of the series, Dennis and Dave cover how to prioritize work being done to maximize return. During […]