Comments (6)
Those are good points, how about something like this?
Even though a surprising number of issues can be planned ahead of time, sometimes things do happen unexpectedly. How does this impact the current sprint if it's already been filled with issues? Well, we call these unforeseen and urgent issues "support issues". Different teams will have different requirements for what support means. Perhaps it means to support the customer. Perhaps it means to support other developers. Our approach to this question is basically this: pick members of the team who will have time allocated to Support Issues over the course of the sprint and allocate some amount of time for them to address Support Issues as they come in. For example, "Dave is estimating 16 hours of support work in this sprint." Support Issues are left undefined at the sprint's outset. As they appear and become defined, they can be routed to the most appropriate team member that has a block of Support Issue work allocated for the sprint.
Maybe take a stab at an alternate if you see something that needs clarification or doesn't make sense. Or if you can see a way to make it shorter, it's rather verbose.
Also, I like the idea of everyone touching support. Particularly in the environment of new product development, it's a great way for everyone working on the product to understand the customer better.
from agilelite.
Thanks everyone, I made some changes, open for input.
from agilelite.
My opinion is that you should avoid adding work to sprints except in exceptional cases. I address the issue of these exceptional cases with this intentionally vague sentence:
Support work is done on a rotating basis because sometimes things do happen unexpectedly and need to be dealt with, but a surprising number of issues can wait until later.
In my experience, development teams never end up with nothing to do and that's part of the problem.
But certainly do the thing that makes the most sense for you. Product breaking bug in production just discovered? Yeah, maybe fix that first! New feature request? Backlog. So it goes.
from agilelite.
@davebs it might be good to clarify or rephrase about support-work. I am all-for your approach of avoiding being over-prescriptive about specific methods. My gut just says the lack of room for support-work would be one of the objections in places where I'd try to implement this (i.e. places that would otherwise be open to all other aspects of it).
I'm fond of Zapier's approach, can summarize or try to make a sentence if you think it's helpful. LMK
from agilelite.
@davebs Here’s a quick riff on that:
Most sprint work can be planned, but sometimes things do happen unexpectedly.
One approach: try support rotations. Some member(s) of the team will allocate time for unplannable Support Issues. These have estimates like other issues, the only difference is the ambiguous or undefined requirement.
Different teams will have different requirements for what support means. Perhaps it means to support the customer/clients. Perhaps it means to support other developers. - rotating everyone through customer support is a great way for everyone to understand the product and clients better.
[👆 maybe there is an inline link to Zapier’s writings, in that sentence.]
It may be good to track the time you dedicate to undefined work, as variations in it can be leading indicators of chronic problems and risks.
from agilelite.
Rotational support sounds like a good idea, but in practice I've seen programmers loathe it. Ad-hoc type of work that support is, differs much from organized sprint work.
There are good arguments for rot. support like everyone learning your product / users, sharing knowledge etc. On the other hand, support is mostly handling defects or odd behaviours if system, not the correct app flow.
For me support is a specialized work, and pushing it to the people working in a sprint can be a serious cause of burnout. Think of the SLA-induced stress, interruptions and re-learning of the same knowledge, picking up work after different colleagues etc.
from agilelite.
Related Issues (20)
- How would this ever work? HOT 3
- A light-weight agile process that's concise, open, easy to learn and understand, and rigid enough to follow that actually works?
- New name? HOT 4
- Spanish translation HOT 1
- No retrospectives? HOT 1
- Why 3 weeks sprints? HOT 1
- It is unclear what an "off week" is HOT 1
- No justifications around any timeframes HOT 1
- Assigning tasks to developers? HOT 1
- Why a week planning for a 3 week sprint? HOT 1
- Waterfall? HOT 3
- Months are not 4 weeks long HOT 2
- Optimal Issue Length HOT 2
- Sorry, but you are wrong! HOT 2
- About the sprint immutability HOT 4
- Constructive alternatives to standups (etc), maybe HOT 2
- Change sprint to iteration HOT 1
- Has this been actually tried in any existing product/team or this is just a vague idea of how this could possibly work? HOT 1
- Persian translation HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from agilelite.