Devops for Growth
112.5K views | +1 today
Follow
Devops for Growth
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: 'scrum'. Clear
Scooped by Mickael Ruau
October 14, 2021 8:04 AM
Scoop.it!

Better Scrum Through Essence

Better Scrum Through Essence | Devops for Growth | Scoop.it
Key Takeaways

Scrum is simple but hard to master. Teams need more help to achieve the full benefits of Scrum.
The freely available Essence Scrum Essentials practice family can help teams to focus and improve their Scrum.
Essence cards and games can help bring training courses and retrospectives to life.
Essence cards and games can help teams to configure and set up their Scrums.
Once the essentials are in place additional practices can help teams take their Scrum to the next level.
No comment yet.
Scooped by Mickael Ruau
October 11, 2021 2:19 AM
Scoop.it!

How To Make Distributed Teams Work

How To Make Distributed Teams Work | Devops for Growth | Scoop.it
Discover key strategies - learn how to leverage Scrum to ignite distributed teams.
No comment yet.
Scooped by Mickael Ruau
October 8, 2021 4:06 PM
Scoop.it!

PRINCE2 and Scrum, Integration

PRINCE2 and Scrum, Integration | Devops for Growth | Scoop.it
The big question: should PRINCE2 and SCRUM be integrated?

It seems a merger of the two could create an optimum solution for product development as well as maintaining a level of governance.

Project Governance is required because questions like the following must be answered:

Are the goals and objectives of the suggested idea in line with company strategy?
Do we have the capability to deliver?
Who has the final decision rights to approve the go ahead and apportion company budget to a project?
Under what framework will the project be governed?

Agile principles and processes do not help in answering these questions so appropriate governance must operate so that risk is minimized, avoid ambiguities, provide structure etc. Of course these are all provided by PRINCE2.

Agile provides a mechanism to deal with change or maintain a close collaboration with customers. It also helps productivity by shielding the development team from bureaucratic processes.

PRINCE2 recognizes that estimates are educated guesses and provides a mechanism to handle that. It makes use of budget tolerances and schedule estimates but on the other hand Scrum uses velocity (an estimate of the pace the team was able to deliver a finished product) that is adjusted at the end of each Sprint.
Mickael Ruau's insight:

Donc, comme les autres méthodes "hybrides" de gestion de projet, Prince2 ne fait pas confiance aux équipes auto-organisées pour s'aligner avec la stratégie d'entreprise et mesurer la capacité à livrer.

No comment yet.
Scooped by Mickael Ruau
September 29, 2021 7:02 AM
Scoop.it!

Différence entre méthode, méthodologie et modèle - Méthodes

Différence entre méthode, méthodologie et modèle - Méthodes | Devops for Growth | Scoop.it
C'est une question qui a été posée dans un concours: Quelle est la différence entre une méthodologie, une méthode et un modèle?
Mickael Ruau's insight:

Un modèle est ce qui a servi de base à l'établissement d'une méthodologie.

  1. On établit le modèle (par exemple du proceccus d'un développement d'un logiciel), donc théorique
  2. On en déduit une méthodologie , c'est à dire une série de principes pour arriver à ce modèle
  3. On en déduit une méthode, qui est comment appliquer ces principes dans la vraie vie







Exemple :

modèle : développement au plus proche de l'utilisateur
méthodologie : agile
méthodes : RUP, XUP, Scrum, ..., ...

No comment yet.
Scooped by Mickael Ruau
September 27, 2021 1:34 AM
Scoop.it!

Scrum e-books

Scrum e-books | Devops for Growth | Scoop.it
Many people like to have formal documentation to read about Scrum. There are many books that you can buy and there are also many great free resources on the web. We can recommend the following FREE downloadable booklets: “Do Better Scrum“ by Peter Hundermark, a CSC and CST in Africa and Brazil. Provides a set of […]
Mickael Ruau's insight:
Some more FREE downloadable booklets on advanced topics:
No comment yet.
Scooped by Mickael Ruau
July 24, 2021 7:50 AM
Scoop.it!

Accidental Adoption: The Story of Scrum at Amazon.com

Accidental Adoption: The Story of Scrum at Amazon.com | Devops for Growth | Scoop.it
Download Citation | Accidental Adoption: The Story of Scrum at Amazon.com | By late 2004, Scrum had been chosen independently as a development process by several teams at Amazon.com. From then until 2009, Scrum spread to a... | Find, read and cite all the research you need on ResearchGate
No comment yet.
Scooped by Mickael Ruau
June 10, 2021 3:27 AM
Scoop.it!

Shape Your ‘New Normal’ With Individuals And Interactions In Mind

Shape Your ‘New Normal’ With Individuals And Interactions In Mind | Devops for Growth | Scoop.it
Scrum Inc. CEO JJ Sutherland examines a fundamental truth all organizations should remember when deciding what their ‘new normal’ will be.
No comment yet.
Scooped by Mickael Ruau
March 17, 2021 10:17 AM
Scoop.it!

Scrum in Sales: Monotype

Scrum in Sales: Monotype | Devops for Growth | Scoop.it
How to implement Scrum in Sales. Learn the three step process Monotype used to level up their sales teams.
No comment yet.
Scooped by Mickael Ruau
February 1, 2021 5:54 AM
Scoop.it!

Negative Sounding Agile Terms, But Are Not

Negative Sounding Agile Terms, But Are Not | Devops for Growth | Scoop.it
If you are new to an Agile team, you may face some confusion with the use of specific terminologies.
No comment yet.
Scooped by Mickael Ruau
November 3, 2020 2:45 AM
Scoop.it!

Misconceptions About Scrum By the Book | by Jasper Bogers | Serious Scrum | Oct, 2020

Misconceptions About Scrum By the Book | by Jasper Bogers | Serious Scrum | Oct, 2020 | Devops for Growth | Scoop.it
In every organization and in every team, I run into one or two customs that people tell me are part of “Scrum by the book”, that aren’t actually in the book. The book I’m referring to in this case is…
No comment yet.
Scooped by Mickael Ruau
October 28, 2020 3:11 AM
Scoop.it!

So you think Scrum = Agile training wheels? | by Willem-Jan Ageling | Serious Scrum

So you think Scrum = Agile training wheels? | by Willem-Jan Ageling | Serious Scrum | Devops for Growth | Scoop.it
Every once in a while I come across the interesting notion that Scrum is “Agile training wheels”. Scrum would be the ideal framework to start Agile. I do understand where this is coming from, but I…
No comment yet.
Scooped by Mickael Ruau
October 6, 2020 4:37 AM
Scoop.it!

Radically Collaborative Patterns for Software Makers | VMware Tanzu

Radically Collaborative Patterns for Software Makers | VMware Tanzu | Devops for Growth | Scoop.it
Get a unique collection of radically collaborative patterns for building software with others. In this mini-encyclopedia, third-generation programmer Matthew Parker introduces you to 27 successful patterns used in organizations that follow distinctive methodologies such as Scrum, Extreme Programming, SAFe (Scaled Agile Framework), and others.
No comment yet.
Scooped by Mickael Ruau
September 23, 2020 11:49 AM
Scoop.it!

Le scrum efficace : FoodMeUp fait des sprints et les réussit

Le scrum efficace : FoodMeUp fait des sprints et les réussit | Devops for Growth | Scoop.it
Comment FoodMeUp a réussi à comprendre le scrum pour rendre le développement logiciel efficace
No comment yet.
Scooped by Mickael Ruau
October 13, 2021 6:28 AM
Scoop.it!

How to use Evidence-Based Management and Scrum (Part 1): Bridging EBM goals with the Scrum Guide  | Scrum.org How to use Evidence-Based Management and Scrum (Part 1): Bridging EBM goals with the Sc...

How to use Evidence-Based Management and Scrum (Part 1): Bridging EBM goals with the Scrum Guide  | Scrum.org How to use Evidence-Based Management and Scrum (Part 1): Bridging EBM goals with the Sc... | Devops for Growth | Scoop.it
This part I of a three-part series will focus on goals. We’ll examine how the goals set out in the EBM guide correspond to the Scrum Guide and some tools and formats for setting workable goals. Part II will focus on experimentation, and Part III will focus on measurement. This part I of a three-part series will focus on goals. We’ll examine how the goals set out in the EBM guide correspond to the Scrum Guide
No comment yet.
Scooped by Mickael Ruau
October 8, 2021 4:08 PM
Scoop.it!

Can PRINCE2 and SCRUM work together?

Can PRINCE2 and SCRUM work together? | Devops for Growth | Scoop.it
In theory, they could be used both because:

PRINCE2  about managing the project’s process.
SCRUM about delivery

How can I relate the different aspects?
For example, is correct
Project Product Description --> Stories, Task ?
 
Is there a document explaining how to relate them?
Mickael Ruau's insight:

 

10:30 am December 15, 2019

of course you can make Scrum and Prince2 work somehow together, but if you combine them you will have a big risk the organization sees Scrum as only software delivery framework.

In that case the scrum team will f.e not be able to do a proper product development or the Scrum Master gets no support for removing impediments outside of the team.

That's something I learned.

 

 
06:55 am December 23, 2019

In companies where the figure of the project manager exists, they certainly cannot be fired.

I think this is the wrong approach.

Certainly, we shouldn't default to letting people go without trying to find a better option, but any transformation is inherently disruptive.
There will be many skilled people within an organization whose existing role becomes obsolete, or even destructive to the new approach; but that doesn't mean we need to keep them working in the same way.
I've worked with Project Managers who have the necessary skills and mindset to become good Product Owners and Scrum Masters. Some might even have other expertise, such that they could join the Development Team as a Business Analyst, UX designer, or engineer.
Some might move to other parts of the organization, such that they are no longer involved with the product.

But if the organization does its best to bring people along, and they are unable or unwilling to keep the organization moving forward, why shouldn't their job security be up for debate?

Failure to deal with such issues is a lack of leadership and could sink an organization.

As unwillingness and an inability to adapt are rewarded, you risk the loss of your most motivated and competent staff.

No comment yet.
Scooped by Mickael Ruau
October 8, 2021 4:00 PM
Scoop.it!

PRINCE2 and Scrum - How to Create the Perfect Hybrid Project | UK

Tactic 1 – PRINCE2 as a utility player

The trick with any PRINCE2 project is to only use the processes you need. That’s why one method is to use Scrum but add some stabilising processes from PRINCE2, like the Risk Register or Lessons Log. You can drop these PRINCE2 processes in as and when you need them, like a utility player. If you want an agile environment with some more assurances, this is the way to do it.

You can use the Sprint Backlog to let the product owner know how much effort these processes require. Then, you can weigh up how valuable they are. You might find, for example, that the Issue Log is easy to fill out during the Daily Scrum and it’s worth having it all documented. On the other hand, maybe the Sprint Review meetings negate the need for a PRINCE2-style Highlights Report. What you keep and what you scrap will really depend on the environment.

Tactic 2 – PRINCE2 as a coach

Another method is to restrict Scrum to Work Packages. Here, you run a PRINCE2 project. The only difference is that the Work Package execution and delivery are done in Scrum. Here, PRINCE2 does everything except for the on-the-ground project work. This works well because Scrum is about project delivery and PRINCE2 doesn’t specify the technical ‘how to’. This is ideal for more PRINCE2-focused environments.

The reason you’d treat a Work Package like a sprint is to make the development process agile. This lets PRINCE2 project managers leverage one of agile’s best advantages: swift delivery. At the same time, you retain the Business Case, defined responsibilities and other advantages of a PRINCE2 project.
No comment yet.
Scooped by Mickael Ruau
September 29, 2021 4:35 AM
Scoop.it!

Loi de Bushnell — Wikipédia

Loi de Bushnell - Wikipédia

All the best games are easy to learn and difficult to master. They should reward the first quarter and the hundredth. - Nolan Bushnell " Les meilleurs jeux sont ceux qui sont faciles à appréhender mais difficile à maîtriser. Un tel jeu sait récompenser aussi bien les débutants complets que les experts.

No comment yet.
Scooped by Mickael Ruau
July 31, 2021 7:54 AM
Scoop.it!

Scrum at Amazon – Guest Post by Alan Atlas

Scrum at Amazon – Guest Post by Alan Atlas | Devops for Growth | Scoop.it

Rally's Alan Atlas shares with us his experience as the first full-time Agile trainer/coach with Amazon. His account is both enlightened and enlightening. He connects the "hows", "whats" and "whys" of Scrum in the Amazon context, making sense for the reader of what took place and what did not at Amazon. You will find additional insights…

Mickael Ruau's insight:

The success of Scrum at Amazon validates one easy, frictionless way to begin a Scrum transition.

  1. Establish stable teams
  2. Make Agile and Scrum information widely and easily available
  3. Give permission to adopt Scrum

The advantage of this approach is that it requires a minimum of enterprise-wide planning and it allows teams to select Scrum, rather than mandating it. All of the rest of an enterprise Scrum transition can be accomplished by simply responding to impediments as raised by the teams and providing management support for change. Based on experience, the impediments raised will include demand (pull) for coaching, scaling, training, organizational change, a Transition Team, PMO changes, and all of the other aspects of an enterprise transition that many organizations labor so mightily to plan and control. Leadership for this kind of transition can only be Servant Leadership from the C-level, which is exactly the right kind for an Agile initiative, isn’t it?

The only impediment to Scrum adoption at Amazon was lack of knowledge.

No comment yet.
Scooped by Mickael Ruau
July 12, 2021 7:37 AM
Scoop.it!

How Amazon & Spotify Use Scrum | Agile Working Case Study

How Amazon & Spotify Use Scrum | Agile Working Case Study | Devops for Growth | Scoop.it
Scrum Case Study: Here's an in-depth look at how Amazon & Spotify used Scrum to increase their productivity & what you can learn to be like them
Mickael Ruau's insight:

Amazon and Spotify have very different approaches as far as the adoption of Scrum is concerned. In the case of Amazon, the organisation allowed adoption to happen incrementally and at the ground level, as demand drove it. In the case of Spotify, it was a deliberate, management-sanctioned plan that led to Scrum implementation.

However, the two businesses are similar in how they use the process. Scrum is used in order to allow teams to be autonomous and self-directing. Spotify’s approach allows them to emphasise autonomous and discrete teams that work separately from others. Amazon’s use of Scrum is focused on long-term, stable teams.

In addition, Amazon’s practice focuses on sharing knowledge and driving better understanding through resources like training, email-based communities, and expert coaches. For Spotify, the removal of roadblocks is vital for rapid responses, product iterations, and scaling up.

No comment yet.
Scooped by Mickael Ruau
March 29, 2021 9:27 AM
Scoop.it!

Changes in the 2020 Scrum Guide: Q&A with Ken Schwaber and Jeff Sutherland

Changes in the 2020 Scrum Guide: Q&A with Ken Schwaber and Jeff Sutherland | Devops for Growth | Scoop.it
The Scrum Guide has been updated to make it less prescriptive, using simpler language to address a wider audience. These changes have been done to make Scrum a “lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems”. An interview with Ken Schwaber and Jeff Sutherland about the changes to the guide.
Mickael Ruau's insight:

Key Takeaways

  • Over the years, the Scrum Guide started getting a bit too prescriptive. The 2020 version brings Scrum back to being a minimally sufficient framework by removing or softening prescriptive language.
  • The 2020 Scrum Guide has placed an emphasis on eliminating redundant and complex statements as well as removing any remaining inference to IT work, and is now only 13 pages long.
  • The 2020 version brings together everyone as one team, the Scrum Team, while previous versions had the Development Team within the Scrum Team.
  • The three artifacts, Product Backlog, Sprint Backlog and Increment now contain ‘commitments’ to them. For the Product Backlog it is the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done.
  • It is important for teams to remember that Scrum is still Scrum. Scrum is a framework. It describes the bare minimum to enable a team to work on complex work.
 

The Scrum Guide has been updated to make it less prescriptive, using simpler language to address a wider audience. These changes have been done to make Scrum a "lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems".

The changes between 2017 and 2020 Scrum Guides are:

  1. Even less prescriptive
  2. One team, focused on one product
  3. Introduction of product goal
  4. A home for Sprint Goal, Definition of Done, and Product Goal
  5. Self-managing over self-organizing
  6. Three sprint planning topics
  7. Overall simplification of language for a wider audience
No comment yet.
Scooped by Mickael Ruau
March 11, 2021 9:05 AM
Scoop.it!

Scrum Success: Embracing The Ability To Adapt

Scrum Success: Embracing The Ability To Adapt | Devops for Growth | Scoop.it
Scrum Inc.’s Jack Harmening and Kendra West share this scrum success story of what teams can accomplish when they're empowered to adapt in trying times.
No comment yet.
Scooped by Mickael Ruau
January 18, 2021 7:41 AM
Scoop.it!

Scrum Commitments — Delving into the Scrum Guide 2020

Scrum Commitments — Delving into the Scrum Guide 2020 | Devops for Growth | Scoop.it
Scrum Commitments: Tying Loose Ends and Shoehorning the Definition of Done — Age-of-Product.com analyzing the Scrum Guide 2020.
No comment yet.
Scooped by Mickael Ruau
October 30, 2020 2:14 AM
Scoop.it!

How to create smarter products that customers like

How to create smarter products that customers like | Devops for Growth | Scoop.it
How successful was your last product release? Did customers respond negatively (or not at all), sales dip or front-line teams get hit with cranky feedback from users? Start avoiding this scenario by incorporating more discovery into your product development process.
No comment yet.
Scooped by Mickael Ruau
October 20, 2020 4:28 AM
Scoop.it!

Robert C. Martin Series Series | InformIT

Robert C. Martin Series Series | InformIT | Devops for Growth | Scoop.it
The Robert C. Martin Series is directed at software developers, team-leaders, business analysts, and managers who want to increase their skills and proficiency to the level of a Master Craftsman. The series contains books that guide software professionals in the principles, patterns, and practices of programming, software project management, requirements gathering, design, analysis, testing and others.

View these Prentice Hall titles, also part of The Robert C. Martin Series today:
• Agile Software Development, Principles, Patterns, and Practices
• Agile Software Development with SCRUM
• Extreme Software Engineering A Hands-On Approach
No comment yet.
Scooped by Mickael Ruau
October 5, 2020 4:44 AM
Scoop.it!

Faire face aux urgences dans les équipes Agile — Wiki Agile du @GroupeCESI

Faire face aux urgences dans les équipes Agile — Wiki Agile du @GroupeCESI | Devops for Growth | Scoop.it
Sommaire
1 Le Contexte
2 Le Problème
3 Le But
4 Solution 1 : Faire le tri et rejeter
5 Solution 2 : Faire le tri et reporter la correction dans le sprint suivant au minimum
6 Solution 3 : prévoir une provision pour gérer les problèmes inattendus
7 Solution 4 : Corriger les causes racines, améliorer la qualité
8 Bonus : dimensionner correctement l'équipe
9 Pour finir ... envisager d'utiliser Kanban à la place de Scrum
10 Pour conclure
No comment yet.