After years of training it is clear to me that many people do much better with pictures than they do with text. I myself am a visual learner, which is why in my presentations I shun bullet points in favor of graphics that help most people understand and retain the concepts.
With that in mind, a number of years ago I decided to design a new visual icon language so I could compose a consistent set of graphics to visually represent core agile and Scrum concepts and their applications in the Scrum framework. The end result is the Visual AGILExicon® (pronounced visual agile lexicon), that I use in all of my training materials and in my Essential Scrum book. In this blog I want to give you the keys to interpreting the graphics in the Visual AGILExicon in case you decide to use them in your own presentations (Yes, that’s right. You can download the graphics free of charge! Get the details here.)
The Visual AGILExicon (VAL)
The Visual AGILExicon is comprised of about 40 four-color icons for composing powerful, three-dimensional graphical representations of foundational agile and Scrum concepts, including roles (such as ScrumMaster, product owner, and development team), artifacts (such as product backlog and potentially shippable product increment), and activities (such as sprint planning and sprint review). These core icons can also be combined to create approximately 70 pictures that represent more sophisticated concepts such as the complete Scrum framework (that I will use as my example in this post), portfolio planning, and product backlog grooming activities.
Scrum at a Glance
To illustrate the beauty and the power of the Visual AGILExicon, let me describe how its elements are used to create perhaps the most important image, the Scrum framework overview.
Let me begin by describing the role of colors in the Visual AGILExicon:
- Blue represents scope: the vision, the product backlog items, and so on.
- Green indicates task-level work.
- Orange highlights a process: sprint execution, sprint reviews, etc.
- Light grey designates a sprint.
- Dark grey depicts relative time.
These colors remain consistent throughout the Visual AGILExicon. Remember this Scrum Framework overview picture (Figure 2.3 in my Essential Scrum book) is just one of over 70 composite images that are part of the Visual AGILExicon, and this image is itself composed of a reusable set of over forty icons (all of which are available for you to use).
So, let’s now walk through the Visual AGILExicon’s graphical depiction of the Scrum Framework to better understand the power of this visual language.
The Product Owner
On the far left of the picture is an individual holding a small blue cube. The cube inside the thought cloud represents a product vision—the idea of a future product or service. The individual is the product owner (the guy with the comb over!). The product owner is responsible for formulating and communicating the product vision. The product owner refines the vision through the items in the product backlog.
The Product Backlog
The product backlog icon, shown just to the right of the product owner with the vision cloud, is composed of product backlog items, illustrated as an ordered collection of blue bricks. The visual metaphor is that the larger vision, the blue cube, is broken down into a collection of smaller product backlog items (PBIs), the blue bricks. There can be different types of product backlog items such as: features, defects, technical work, and knowledge-acquisition work. You can read about the different types of product backlog items in my post “Demystifying Product Backlog Concepts.”
You’ll notice that in the product backlog some of the blue bricks are larger and others are smaller. And, some are lighter blue and others are darker blue. As you might suspect, larger bricks are meant to represent larger pieces of functionality and the smaller bricks to mean small pieces. Lighter blue means lightly detailed and darker blue means more detailed.
The blue bricks near the top of the product backlog—the high-priority PBIs—are smaller and darker blue, representing product backlog items (scope) that are in a state I call ready. You can read more about what it means for a PBI to be ready in my post “Definition of Ready.”
The blue bricks at the bottom of the product backlog, on the other hand, are lower in priority, so these PBIs can be bigger and less detailed. As such, they are represented as larger and lighter blue bricks (not ready to be moved into a sprint).
Product Backlog Grooming (Refinement)
The process by which the vision and larger product backlog items are progressively refined into smaller ready items is called product backlog grooming (or product backlog refinement). The grooming process is represented by an orange arrow (remember orange in the Visual AGILExicon represents process) that loops in a clockwise fashion around the middle of the product backlog.
Grooming consists of 3 activities:
- Writing PBIs (represented by the pencil and hand icon)
- Estimating PBIs (represented by the two hands with the ruler between them)
- Prioritizing (or ordering) PBIs (represented by the hand sorting the cards)
These activities happen continuously, as the team and the product owner learn more about the product being developed. The product owner and team work together regularly to add new PBIs, break down high-priority PBIs into smaller, more detailed PBIs, discard unnecessary PBIs, estimate (or re-estimate) PBIs, and sort (or re-sort) the PBIs in priority order.
As you examine the Scrum framework picture you will see a large, grey looping arrow that dominates the foundation of this picture beginning at the product backlog and moving underneath or through all of the remaining icons. This arrow represents the sprint, a fixed-length, timeboxed iteration of one week to one month in duration, during which time the team plans, begins, refines, and completes a specific set of potentially shippable product functionality, then inspects and adapts both the product and the process before beginning the next sprint.
Notice that the sprint arrow has multiple dark grey sections under the process (orange) icons. The extent of each dark grey section is intended to provide a rough idea of how much time the team will spend in each activity. The larger the darker grey section, the more time the team spends in that activity.
Also notice that in the grey sprint arrow surrounds an icon composed of three “people.” This icon is meant to represent the Scrum team, which includes the product owner, ScrumMaster and the development team roles. We’ve already met the product owner—that’s the guy with the comb over holding the blue cube. The ScrumMaster is the lady wearing the coach’s whistle; and the third icon is for the development team. In this visual representation, the development team is depicted as a lady with a collection of green cubes (which represent tasks – to be discussed shortly). In other images in the Visual AGILExicon the team is depicted as a collection of people (see image below).
The placement of this Scrum team icon is meant to convey that the entire Scrum team is involved or invited to each activity that takes place within the sprint. (For a closer look at who should be at each sprint meeting, I refer you to the blog post, “Who Should Attend Scrum Meetings?”)
Let’s continue our visual walk around the Scrum framework.
The icon to the right of the product backlog represents sprint planning – visually depicted as two connected orange arrows. The visual metaphor is that those two connected arrows bound a capacity – the team’s capacity to do work this sprint. The goal of sprint planning is for the development team to pull high-priority ready items (small dark blue bricks) from the product backlog. The items that are pulled by the team represent the work that the team believes it can accomplish this sprint.
Notice that pulled blue bricks don’t completely fill-up the space bounded by the two orange arrows. In other words, the pulled blue bricks occupy most, but not all, of the teams capacity. The unoccupied space in the icon is a visual representation of the buffer that the team should leave uncommitted to account for unpredictable events. The exact size of that buffer will differ from team to team and from organization to organization.
Sprint planning is the first activity in every sprint. It is timeboxed to 4-8 hours depending on the length of the sprint itself (that amount of time is visually represented by the darker grey are on the sprint arrow directly below the sprint planning icon.
The sprint backlog is the next icon we come to in the Scrum framework graphic. The members of the development team often create a sprint backlog as a means of acquiring confidence that the commitment the development team is making during sprint planning is a reasonable one (you can read more about this concept in my blog, “Sprint Backlog: An Artifact for Acquiring Confidence.”)
Let me explain the sprint backlog icon. It looks like a table with blue bricks and green cubes. We know that blue bricks are product backlog items, and in the sprint backlog, the blue bricks are the specific PBIs that were pulled into the sprint during sprint planning. Green cubes represent tasks (e.g., design, build, test, and integrate work). The visual metaphor is that each blue brick is broken down into a collection of green tasks. Teams break PBIs into tasks to understand the work involved in completing a given PBI—and ultimately how many and which PBIs the team feels confident it can complete during the sprint, given the team’s capacity.
The next icon in the graphic represents sprint execution, a term I use to refer to the period of time during which the team is doing design, build, test, and integrate work. In graphical terms, the team members are doing the green cube work that makes up each blue brick in order to complete the PBIs the team committed to during sprint planning.
SIDE BAR: This is a good time for me to point out a large difference between the Visual AGILExicon representation of the Scrum Framework and many other visual representations. The majority of Scrum framework pictures do not have a visual representation for sprint execution (see example picture below).
Source: Wikipedia (Scrum)
Instead they conflate the sprint (which I show as the large grey arrow) with sprint execution. In the above picture, and the many like it, the large circular arrow (with “30 days” inside it) means the “sprint”, and not “sprint execution.” The Visual AGILExicon has separate visual representations for both sprint and sprint execution. You will also notice that in the above picture, and the many like it, there are no representations for the sprint review or sprint retrospective. The Visual AGILExicon formalizes and visualizes both of these activities as part of the sprint.
One of the repeating activities that happens during sprint execution is the daily inspect-and-adapt meeting known as the daily scrum. In the Scrum framework graphic, the daily scrum is shown as two orange connecting and looping arrows (an inspect arrow and an adapt arrow) that are attached to the sprint execution icon. Inside the connected daily scrum arrows is the sprint backlog icon. The sprint backlog icon is placed there to signify that during each daily scrum meeting, the team inspects the work to date on the items in the sprint backlog and adapts as needed to ensure the team meets the sprint goal. There are a number of approaches for performing the daily scrum that you can read about in my post “Understanding the Daily Scrum – Rules and Misconceptions.”
Potentially Shippable Product Increment
Just after the sprint execution icon is the icon for the potentially shippable product increment. The visual metaphor for this icon captures the idea that, by the end of the current sprint, the development team has completed a piece of the larger vision (a piece of the larger blue cube). That piece (typically several product backlog items – shown as blue bricks inside the larger blue cube) needs to be done to the Scrum team’s agreed upon definition of done. Potentially shippable does not mean you actually have to ship, deploy, or release it. Shipping something is a business decision, so it ought to be based on business factors. Potentially shippable is better thought of as a state of confidence: how confident are you that if shipping something were the right thing to do at the end of this sprint, we could do it.
Continuing along the grey sprint arrow, the next icon is the sprint review. The sprint review is another of the Scrum inspect and adapt activities. So, the icon for the sprint review is similar to the inspect and adapt icon used for the daily scrum, except this time the focus of the inspect and adapt activity is the work that the team has completed. The sprint review is illustrated by taking the completed piece of the blue cube from the potentially shippable product increment, and making that the focus of the sprint review. This visual representation supports the intent of the sprint review—give everyone with input into product development an opportunity to inspect and adapt the product. For more information on the sprint review and a discussion on why I don’t call this a sprint demo, see the blog, “It’s a Sprint Review, Not a Sprint Demo!”)
The final icon in the Scrum framework graphic is the sprint retrospective. The sprint retrospective is a time for the Scrum team to inspect and adapt its process. What is working? What isn’t working? What should we change? The sprint retrospective is another inspect-and-adapt activity, so it reuses the orange inspect-and-adapt arrows that were used in the daily scrum and the sprint review icons. The visual pattern for all inspect-and-adapt activities is to have the orange inspect-and-adapt arrows surrounding some object that is the focus of the inspect-and-adapt activity. In the case of the daily scrum, that object is the sprint backlog icon. In the sprint review it is the potentially shippable increment piece of the blue cube. In the case of the sprint retrospective it is a new orange gear icon that fills that object role. This gear is meant to represent the entire Scrum process, since the retrospective is focused on inspecting and adapting any aspect of the Scrum process.
Browse or License the Visual AGILExicon®
Okay, so my goal for this blog was to introduce you to the visual language that underlies the Visual AGILExicon. I singled out the Scrum framework image to describe many of the visual metaphors that are used consistently throughout the full set of images in the Visual AGILExicon.
These pictures, which I created for my book Essential Scrum (and which are available to license and download), were a joint venture between me and a fantastic graphics artist named Jeff Schaich. The development of the language was very iterative. I would describe the concept of what I was trying to achieve and Jeff would come up with visual ideas for how to represent those concepts. I would then select candidate ideas and we would iterate designs.
As with any reusable asset, I needed to keep iterating until we had used each icon in several compositional pictures to know whether or not the icon we had conceived was useful and reusable. I was leveraging an old adage from my Smalltalk days: “You don’t know that something is reusable until you have actually reused it several times. And, be prepared to build it at least three times before you have something that is reusable.” That is pretty much how it went with the icon-language design.
In truth, I invested an enormous amount of time in creating the Visual AGILExicon for use in my book and presentations. I think that in the three years it took to write and edit Essential Scrum perhaps as much as 50 percent of the overall effort went into the creation and refinement of the images. And it was worth it. To me the book would be a mere shadow of itself if it did not include the over 200 pictures that it has. As I mentioned, any agile practitioner can get a no-cost license to use the four-color* Visual AGILExicon images in their own presentations or on their intranets (use of the images on public websites is not permitted at this time). To learn more about the Visual AGILExicon visit: http://www.innolution.com/resources/val-home-page.
I hope you find the Visual AGILExicon® helpful in understanding Scrum and in explaining it to others. Also, if you want to get a more complete description of the Scrum framework picture that I used in this post, you can read Chapter 2 of Essential Scrum. You can download a free copy of that chapter by signing up for my Newsletter!
* Quick note: There are also two-color versions of each Visual AGILExicon image that I use in my Essential Scrum book (the book is published in two colors not four colors). However, the images I make available for people to use are the visually more appealing four-color versions.