55289Re: [scrumdevelopment] Express checkout during a sprint
- Jun 12, 2012...and one more thing I don't think anybody mentioned yet.Can the "new customer signup/integration" be more automated? It seems like the cost of interruptions, combined with the sales team being able to promise a quicker lead time to start using your app, might help justify the automation of the process.-------
From: Charles Bradley - Scrum Coach CSP CSM PSM I <chuck-lists2@...>
To: "firstname.lastname@example.org" <email@example.com>
Sent: Tuesday, June 12, 2012 7:22 AM
Subject: Re: [scrumdevelopment] Express checkout during a sprint
This is my preferred way of handling production support:http://www.scrumcrazy.com/One+way+to+handle+Bugs+and+Production+Support+in+ScrumI have concerns similar to others about you moving to 2 week sprints, but I also think that the frequency and resolution time of these "critical" issues is what would sway me to go one way or the other (assuming all other things equal).For instance, if on average:
Like others, I believe all of these occurrences should be retrospected on.
- ~1 interruption every 2 weeks taking on average one day to resolve by 1-2 people -> indicates(all other things assumed equal) moving to a 2 week sprint is probably no big deal
- ~4 interruptions every 2 weeks taking 2-3 days to resolve and/or involving 4 or more people-> indicates 1 week sprints would probably be better.
- somewhere between those two extremes -- judgement call, try, inspect and adapt.
When it comes to interruptions like these, I personally believe that each interruption should be automatically discussed in a retrospective to find the root cause and some possible solutions -- because most of them are solvable or at least mitigatable. Having said that, I also don't think this policy should be dictated to the team, so instead, as a Scrum Coach, I strongly encourage the team to discuss them.
From: fortheloveofmathematics <omaeva@...>
Sent: Tuesday, June 5, 2012 5:57 PM
Subject: [scrumdevelopment] Express checkout during a sprint
How does everyone handle high priority items that come in during the middle of a sprint?
Currently both of my teams run one week sprints. Coming up we will be all switching to two week sprints because of the type of work we are doing.
Now a few of our product people are worrying that they won't be able to get high priority items in mid-sprint. Part of this is unavoidable because we make all our revenue on advertising and when a deal is made we have strict deadlines.
I would prefer not interrupt sprints for that kind of stuff, and mentioned we could possibly allocate 10-15% of our sprint to those type of items and if they don't arise work on our tech debt.
Any other ways of handling that?
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
- << Previous post in topic Next post in topic >>