3581RE: [scrumdevelopment] Planning multiple sprints
- Jun 5, 2004
MessageBaboo:We have done things like this since 1996 (Mercer, Nike Securities,Lincoln Reinsurance, Caremark, Hipaa Accelerator, New Governance, etc.)Here are few answers to your questions:1. The Scrum masters in each team are the Project Managers (with thenew Scrum attitude and responsibilities that Scrum REDEFINES)2. There is optionally a Scrum Master for the Shared Services(or sometimes called architecture team), this applies specially if your applicationsuse shared components (databases, app servers, transaction managers,security, workflow, and other services)3. the combined backlog of all project including Shared Servicesis the "global backlog"4. each project manages its own backlog but has in it often"shared components" tasks5. the shared backlog is maintained by the Shared Services team6. The technical leads of every team belong to the "architectureteam"7. There is optionally a "Shared Services" technical lead, (sometimescalled an "enterprise architect"8. The technical leads meet at least once a week for a "technicalshared scrum"9. The Scrum Masters of every team meet in a Scrum of Scrums atleast once a week to discuss:- dependencies- responsibilities for shared components- conflicts- possibilities for reuse-10. The "Shared Services" team offers help to other teamsoften by borrowing "technical leads" and/or developers to themAt Caremark we had up to 17 teams working under this system. At New Governancewe have had up to 5 teams working using this system.Also, the evolution of 1 scrum team into multiple dependent teams is discussedin Ch 7 of the first Scrum book.We are proposing to use this management system to our customers/prospectsto manage the governance and enterprise compliance of Fortune 500 companies.There is more information about this at:(was XBreed)(We don't actively sell consulting services in this area anymore since wehave become a "software company" http://www.newgovernance.combut I keep the website mainly to make this information available to others that couldpotentially benefit from this information.)- Mike
** We have renamed our company and realigned our focus into
the broader Compliance and Governance markets. Our email and
web site at Hipaa Accelerator will stay current and will
be redirected to our corresponding New Governance addresses.
Michael A. Beedle Ph. D.
New Governance Inc.
2275 Half Day Rd. Suite 350
Bannockburn, IL 60015
http://www.newgovernance.com-----Original Message-----Hi there,
From: Baboo Kureemun [mailto:baboo.kureemun@...]
Sent: Friday, June 04, 2004 11:21 AM
Subject: [scrumdevelopment] Planning multiple sprints
We are new adepts of scrum, and this is our third month into it. Our
first month started with one sprint for one of our teams. In the second
month, we had three teams, hence three daily scrums. We are continuing
in that same vein for the current month. We just came out of
effort-draining planning sessions given that the three sprints start on
the same day (hence, they end on the same day). Here are some questions
(probably bantered with before) that I would be grateful having some
(a) Before scrum, we had a (technical) team lead in charge of the
technical (programming-side) aspects within each team, and a project
manager (less technical/more managerial) co-ordinating the efforts among
projects as well as the QA team. Who would qualify for the scrum master?
Would this be the team lead? Or, would this be the project manager (who
is neither developing, nor testing nor tech writing? What are the
'qualifications' of a scrum master?
(b) We are currently following the rule of the calendar month aligned
with the sprints. This means that three sprints start together, and end
together. The product owner goes to three sprint reviews and three
sprint planning sessions between sprints ... any thoughts as to whether
it makes sense staggering the sprints? ... Anybody tried that? Can a
sprint be defined as a 30-day cycle that starts on any date with no
bearing on the calendar month?
Thanks for clarifying,
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...
- << Previous post in topic Next post in topic >>