Devops for Growth
107.5K views | +8 today
Follow
Devops for Growth
Technology
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'sprint'. Clear
sprint 13
scrum master 7
product owner 4
PSM2 4
PSM1 2
scrum 2
coaching agile 1
dynamique d'équipe 1
psm3 1
PSPO 2 1
sauvetage de projet 1
scrum team 1
Scooped by Mickael Ruau
Scoop.it!

La magie des Sprints de 1 jour ! –

La magie des Sprints de 1 jour ! – | Devops for Growth | Scoop.it
From dantotsupm.com - November 10, 2021 12:24 AM


Dix sprints de 1 jour vous permettent d’achever 10 cycles de travail et d’apprentissage ensemble, 10 fois plus rapidement qu’une équipe typique. Et cela vous force à identifier les compétences et pratiques critiques comme trouver de petites poches de valeur et collaborer ensemble sur quelque chose au lieu de juste de remettre son travail de l’un à l’autre en séquence, ignorant facilement les compétences et pratiques dans un sprint de 2 semaines.

Vous dépenserez plus de temps dans les cérémonies de sprint. Aussi, ne devriez-vous probablement pas les adopter pour toujours. Mais si vous ressemblez à mes clients, vous serez étonnés de constater combien vous aurez réalisé.
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Product Goal & Sprint Goals – A Simple Example

Product Goal & Sprint Goals – A Simple Example | Devops for Growth | Scoop.it
From www.thescrummaster.co.uk - July 27, 2021 1:24 AM
Here are some simple examples of Product Goals, Sprint Goals and the relationship between them.
Mickael Ruau's insight:

Here are some simple examples of Product Goals, Sprint Goals and the relationship between them.

We will stick with our Bakery example (as used previously in our simple example of a Definition of Done).

Some things to note:

  • Our Bakery produces baked goods sold in our shop to passing customers.
  • We already have the capability to deliver products inside London that are ordered in-store.
  • We have 1 cross-functional Scrum Team containing all the skills required.
  • We are looking back at the Product Goals and Sprint Goals that were used once they were all fulfilled or discarded.
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Why using Sprint 0 is a cardinal sin for all Scrum Masters | by Maarten Dalmijn | Serious Scrum

Why using Sprint 0 is a cardinal sin for all Scrum Masters | by Maarten Dalmijn | Serious Scrum | Devops for Growth | Scoop.it
From medium.com - October 19, 2020 8:29 AM
You may think ‘cardinal sin’ is a strong word to use to talk about Scrum Masters that start their teams with Sprint 0. I don’t think so. I believe it is appropriate for the offense. A Scrum Master…
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Examples Of Real Sprint Goals: And the reasoning and considerations that shaped them

Examples Of Real Sprint Goals: And the reasoning and considerations that shaped them | Devops for Growth | Scoop.it
From www.scrum.org - September 16, 2020 1:37 AM
Although most people see the value of Sprint Goals, how to create them is a huge source of confusion and frustration. Is the Spring Goal there before the Sprint Backlog? How do you create a Sprint Goal out of the unrelated set of items at the top of your Product Backlog? And should everything on the Sprint Backlog be related to the Sprint Goal? In this post I work from examples of a real product, and the Sprint Goals we used there, to answer those questions.
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Struggling with Sprint Goals

Struggling with Sprint Goals | Devops for Growth | Scoop.it
From www.scrum.org - September 4, 2020 2:02 AM
Having a Sprint Goal in some cases is not easy. Having a good Sprint Goal is even more difficult.
Mickael Ruau's insight:

Some easy wins might come from creating more focus on the Product Backlog. In essence, you have to start doing less things in parallel:

  • Work for less stakeholders at the same time, just to show you are making progress.
  • Do less epics, projects and features in parallel.
  • Start less stories or items in the Sprint at the same time.
  • Work on some items together instead of everyone doing their own ‘item’.
  • Stop working on many different tasks in parallel, because ‘they look like each other’ or ‘you got stuck’ in one of the tasks. Start finishing tasks and resolve your bottlenecks.

By limiting the amount of different things you work on at all levels, you create focus.

more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Sprint Cancellation

Sprint Cancellation | Devops for Growth | Scoop.it
From www.scrum.org - August 31, 2020 8:39 AM
In this Scrum Tapas video, Professional Scrum Trainer Piyush Rahate provides examples of why a Sprint may be canceled, ways to avoid canceling a Sprint and what might happen if the decision to cancel is made. (4:05 Minutes)
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Scrum from the trenches - the Sprint Goal

Scrum from the trenches - the Sprint Goal | Devops for Growth | Scoop.it
From www.linkedin.com - December 5, 2018 8:54 AM
In the "Scrum from the trenches" blog post series I like to address topics that I encounter in practicing Scrum in the real world, with real teams. Sharing where theory comes into practice, what challenges teams encounter along the way and ways to help Scrum practitioners use the power of empiricism to overcome these challenges.
Mickael Ruau's insight:

Product Owners should share their vision and what goals need to be achieved next. They should talk about it, share it, get feedback on it. Then invite the Development Team to pull work from the Product Backlog (and maybe create some Sprint Backlog Items as well) that will achieve this goal. Share and discuss this when the plan for this Sprint is drafted.

Often, Product Owners take the lead in Sprint Planning. And they should at first, but then they have to let the Development Team self organize around the Sprint goal. You might be surprised at the results!

The key in this situation is to look at the way the work is organized. Is the Product Owner trying to keep all the stakeholders happy by giving them all a breadcrumb? Or are the stakeholders managed and is the Product Backlog organized around functional components that deliver value for customers at the end of the Sprint?

The Product Owner must be challenged on the status quo and the Development Team should take ownership on the plan that should have the Sprint Goal as outcome. They should discuss the Product Backlog Items that are taken into the Sprint and also look for alternative ways to achieve the Sprint goal.

more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Scrum : quel est le bon jour pour commencer un sprint ?

Scrum : quel est le bon jour pour commencer un sprint ? | Devops for Growth | Scoop.it
From blog.talanlabs.com - October 14, 2021 10:26 AM
Quel est le bon jour pour commencer son sprint ? Quelle est la bonne heure pour le daily scrum ?
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

YDS: Can the Sprint Backlog Change During a Sprint?

YDS: Can the Sprint Backlog Change During a Sprint? | Devops for Growth | Scoop.it
From agileforhumans.com - June 22, 2021 10:48 AM

Todd and Ryan discuss how a Sprint Backlog is emergent and how the Developers are encouraged to update the Sprint Backlog as new things are learned about their Product. Check out the video for more tips on how to manage complexity during your product development efforts.

more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Sprint Goal Template

Sprint Goal Template | Devops for Growth | Scoop.it
From www.scrum.org - September 28, 2020 3:21 AM
The template aids the conversation around the "WHY" the team is doing something, and stays away from the "HOW" - as that is likely to change through the sprint.
Mickael Ruau's insight:
 

The first version was this one....

Our focus is on <Achievement>

We believe it delivers <Benefit> to <Customer>

This will be confirmed when <Event happens>

which then evolved into 

Our focus is on <Outcome>

We believe it delivers <Impact> to <Customer>

This will be confirmed when <Event happens>

I've tried the template a couple of times, as well as other Scrum Masters I know. The feedback has been positive. 

more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

The Sprint Goal Lifecycle

The Sprint Goal Lifecycle | Devops for Growth | Scoop.it
From www.scrum.org - September 4, 2020 2:57 AM
In this blog post I explain why the Sprint Goal is key for an effective implementation of Scrum and how it is widely present in the Scrum framework by exploring its “lifecycle”. 
Mickael Ruau's insight:
  • Emerging from the Product Backlog as a business objective expressed by the Product Owner as a value assumption,
  • Created at the Sprint Planning by the collaborative work of the Scrum Team,
  • Going through the Sprint to be implemented into a Done Product Increment by the Development Team as a tangible way to validate the value assumption,
  • Helping the stakeholders in knowing what value will be delivered and having an interest in attending the Sprint Review,
  • Inspected, ultimately, during the Sprint Review, by the Scrum Team and stakeholders, to validate the value assumption,
  • During the Sprint Retrospective, improving ways to better implementing it into a Done Increment with higher quality in future Sprints,
  • Going back to the Product Backlog as a subsequent business objective (Sprint Goal candidate) resulting from the inspection & adaptation done by the Scrum Team and stakeholders.
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

Stop treating your Sprints like Fort Knox | by Maarten Dalmijn | Serious Scrum | Aug, 2020

Stop treating your Sprints like Fort Knox | by Maarten Dalmijn | Serious Scrum | Aug, 2020 | Devops for Growth | Scoop.it
From medium.com - September 3, 2020 3:58 AM
When asking for help you’ll often get a reply along the lines of:

“Why are you bothering us with this now? You could have known about this before. Our Sprint has already started, you’re too late. Our Sprint is full, and we have an important project we need to deliver. Please don’t bother us, and we don’t expect to be able to help you in the next couple of Sprints.”
Mickael Ruau's insight:
Four ingredients of flexibility

For teams to be flexible towards each other, you need four elements:

  1. Sprint Goal. A mandatory, overarching objective that does not utilize the full capacity of the Scrum Team. The Scrum Team only plans at a maximum of 70% capacity to optimize flow and to be able to deal with the unexpected. Fully occupied Scrum Teams will never have room to handle the unexpected or help each other.
  2. Sprint Backlog flexibility. The Sprint Backlog emerges during the Sprint, and the team tries to come up with the least complex way to meet the Sprint Goal. It’s okay if Sprint Backlog items carry-over to next Sprint that do not relate to the Sprint Goal.
  3. Inter-team flexibility. When another team asks for help, you make time to help them out. The default stance should be to collaborate, instead of to negotiate. Of course, if the request puts the Sprint Goal at risk, then it’s a different story. You can still help to the extent that you don’t put the Sprint Goal at risk. You could also make the joint decision to make one Sprint Goal more important than the other, if that results in more value to the company. Of course, this is something for the Scrum Teams (including Product Owners) to decide.
  4. Psychological safety. If teams get punished for taking initiative and making decisions, then you will destroy all initiative. Sticking to the original plan becomes the default option even if it doesn’t make sense.
more...
No comment yet.
Sign up to comment
Scooped by Mickael Ruau
Scoop.it!

10 Powerful Questions to Create Better Sprint Goals

10 Powerful Questions to Create Better Sprint Goals | Devops for Growth | Scoop.it
From www.scrum.org - August 7, 2020 8:31 AM


If we don’t work towards this Sprint Goal, what will be inevitably lost or become much harder later?
If we wouldn’t have another Sprint after this one, what would be the one thing we’d have to deliver in order to return some value?
If we were paying for this Sprint with our own money, what work would give us the highest chance to get that money back?
When we achieve this Sprint Goal, what has clearly changed or improved from the perspective of stakeholders?
Which steps are required to achieve this Sprint Goal? Which are the least required or could we do without if we really have to?
If we suddenly have half the team available and we can do only half the work required for the Sprint Goal, what should absolutely be in there in order for us to still be okay with the outcome? What can we let go of for now and return to later?
If there’s an ‘AND’ in the Sprint Goal: Which would you naturally do first if you have to choose? What is irrevocably lost if we do that thing first, and the second thing in another Sprint?
What would need to happen while working on this Sprint Goal that would be cause for celebration?
What worry about our product is keeping you up at night? What can we build or test this Sprint to make you sleep a bit better?
In terms of value and learning about what else is needed from us a team, what is the worst way to spend the upcoming Sprint? What should we focus on this Sprint to prevent that?

Although these questions don’t give you the Sprint Goal on a platter, they do help you discover what is the most uncertain and valuable right now, and thus input for your Sprint Goal.
more...
No comment yet.
Sign up to comment
About Follow us Resources Terms Mobile Features
Facebook
X
LinkedIn