Seeing The Big Picture With Scrum

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

A common phenomenon happening in organizations implementing scrum is that something is missing – the big picture. People are saying “We used to have High-Level Designs – where are they?”, “We used to have an architecture before developing – where is it?”. The answer will usually be that as we are working with small batches we need to focus on what’s immediately coming up and so other things are getting neglected.

But this is a confusion. Nothing should be neglected. For sure we cannot neglect long-term thinking and planning.

Why are we losing the big picture?

The reason for this confusion is that scrum focuses on the iteration, on the short term. As depicted below.

In the above illustration (taken from Wikipedia) you can see that most of the action is on the right-hand side of the picture. There’s a big circle denoting the iteration (originally it said 30 days, I took the liberty of changing it to 2 weeks) and above it the 24 hours cycle.

Most of the attention is on the cycle of iteration. The scrum events/ceremonies (depending on your school) are all around the iteration.

What doesn’t get attention in most implementations is the arrow on the left, connecting the backlog and the sprint backlog. A lot of stuff is happening on that arrow, depending on the organization, for example:

  •       High-level design
  •       User Experience Design
  •       Reviews

What should happen before the sprint?

The thing that escapes many organizations is that this arrow is not directly related to the iterations but rather is an ongoing process. Something like this:

In addition to the process of the scrum team, there is an ongoing process of high-level designs, architecture, and more – things that usually take more time.

This process – backlog grooming – is where we are cooking the scope on low heat, preparing it for the boil of the iteration. This is where you have time to think, process, to look at the big picture. We shouldn’t overdo this or the scope will get spoiled, of course. We need to do just enough so it will be ready for the teams.

The people involved in this process will be product managers, architects, team leads, experts, and others, some of them from the scrum teams. During planning, some capacity of the teams should be reserved for this.

How should we manage this?

We usually recommend using the Kanban method to manage this process, from end to end. This will help you understand what’s going on around you and control it.

Here is an example flow used by many:

On the left, you can see what’s happening before development. As you see, what’s happening in the iteration is just one column – DEV, one stage in the lifecycle of items.

The idea is that we manage two streams: the iteration stream and the end-to-end stream.

Once you set this board, there’s no going back. Until that moment management was all the time concerned with the various teams’ progress. Once they see the big picture two good things happen: first, management raises their heads, looking ahead, handling big obstacles, and making strategic decisions. The second thing is that teams can finally work quietly without being bothered all the time by questions from management 🙂

Subscribe for Email Updates:

Categories:

Tags:

Keith Sawyer
Tips
Engineering Practices
ART Success
ARTs
EOS®
Continuous Integration
agileisrael
Lean Agile
PI Objectives
TDD
Portfolio for Jira
Legacy Code
SAFe Release Planning
ScrumMaster Tales
ALM Tools
Perfection Game
speed @ scale
Scaled Agile Framework
Reading List
Implementation of Lean and Agile
Limiting Work in Progress
Product Management
Continuous Improvement
RTE Role
Games and Exercises
Kanban
Acceptance Test-Driven Development
speed at scale
Risk Management on Agile Projects
Legacy Enterprise
Agile Marketing
lean agile change management
Agile for Embedded Systems
Agile Outsourcing
Slides
Webinar
Agile Contracts Best Practices
Agile Release Management
Lean Agile Organization
Software Development
Systems Thinking
Amdocs
Lean Agile Leadership
Atlassian
Scrum With Kanban
Operational Value Stream
Certification
Rovo
Lean-Agile Budgeting
Lean Agile Basics
Jira
SPC
Hybrid Work
BDD
Team Flow
Lean Risk Management
Video
Agile Exercises
Large Scale Scrum
ROI
Agile Basics
Release Train Engineer
SA
Agile Israel Events
Jira Cloud
LeSS
Risk-aware Product Development
RSA
Agile Mindset
Lean Startup
A Kanban System for Software Engineering
SAFe DevOps
POPM
The Kanban Method
ATDD vs. BDD
Scrum Primer
Agile Testing Practices
Kanban Game
AgileSparks
Development Value Streams
AI
Kaizen
Agile Product Development
Sprint Planning
RTE
Frameworks
Applying Agile Methodology
Business Agility
Kanban Basics
Achieve Business Agility
System Integration Environments
ATDD
chatgpt
Scrum
Agile
Manage Budget Creation
Advanced Roadmaps
Lean-Agile Software Development
Continuous Deployment
Agile and DevOps Journey
IT Operations
Agile Risk Management
Kanban Kickstart Example
Test Driven Development
System Archetypes
Code
Quality Assurance
Entrepreneurial Operating System®
SAFe
Continuous Planning
Lean and Agile Principles and Practices
predictability
Elastic Leadership
Scrum Values
What Is Kanban
User stories
Agile Product Ownership
Presentation
Managing Risk on Agile Projects
Agile Community
Software Development Estimation
Scrum and XP
Artificial Intelligence
Principles of Lean-Agile Leadership
Nexus
Rapid RTC
PI Planning
Nexus and Kanban
Jira admin
Sprint Iteration
Agile Release Planning
Pomodoro Technique
Implementing SAFe
LPM
Agile Games and Exercises
Sprint Retrospectives
Professional Scrum Product Owner
Atlaassian
Agile India
Nexus vs SAFe
Retrospectives
Lean Software Development
QA
Agile Program
Daily Scrum
Managing Projects
Introduction to ATDD
Nexus Integration Team
Enterprise DevOps
Confluence
Agile Project
NIT
GanttBan
Value Streams
Planning
DevOps
The Agile Coach
Nexus and SAFe
An Appreciative Retrospective
Scrum.org
Agile Israel
WIP
Agility
Kanban 101
Iterative Incremental Development
Scrum Master Role
Professional Scrum Master
Program Increment
Covid19
Process Improvement
Professional Scrum with Kanban
Certified SAFe
Jira Plans
Change Management
Agile Assembly Architecture
Self-organization
Agile Delivery
Accelerate Value Delivery At Scale
Agile Project Management
Kaizen Workshop
LAB
Introduction to Test Driven Development
Agile Development
Agile in the Enterprise
Coaching Agile Teams
Agile Techniques
transformation
Releases Using Lean
Scrum Master
Story Slicing
Risk Management in Kanban
Product Ownership
Agile Games
Tools
System Team
Built-In Quality
Spotify
Lean and Agile Techniques
Lean Budgeting
Scrum Guide
Lean Agile Management
Effective Agile Retrospectives
Continuous Delivery
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart