Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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:

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