 Your new post is loading...
 Your new post is loading...
|
Scooped by
Mickael Ruau
September 23, 2020 1:10 AM
|
Commitment can lead to rigidity when the commitment is set to ‘the plan’ or ‘the destination’, instead of ‘the goal’.
|
Scooped by
Mickael Ruau
August 31, 2020 1:55 AM
|
This article addresses basic remote agile anti-patterns — the pitfalls any distributed team wants to avoid — Age-of-Product.com. #Agileantipatterns #RemoteAgile
|
Scooped by
Mickael Ruau
August 25, 2020 2:09 AM
|
Key Takeaways
The software industry has a dismal track record when it comes to predicting and planning in the face of uncertainty. There are a significant number of biases that prevent us from learning, including cognitive biases and compensation structures. Statistical approaches to predictions can be successful if we expend the effort to create learning-based models such as Monte Carlo simulations. Highly uncertain environments are best exploited using the iterative learning models inherent to Agile methods. Extremely uncertain, non-deterministic environments are best exploited by the incremental learning model of hypothesis testing (Hypothesis-Driven Development) and learning to embrace the discomfort associated with uncertainty.
|
Scooped by
Mickael Ruau
August 17, 2020 1:28 AM
|
Are you interested in a DevOps transformation for your business? Learn how the Garage practices can help!
|
Scooped by
Mickael Ruau
August 10, 2020 1:28 AM
|
"When will it be done?" is a damaging question when dealing with complexity & uncertainty. Leadership needs to be about blaming those who fail to help or who fail to ask for help, over blaming those who fail. According to Richard Hackman's research, over 80% of a team's performance is determined by structure, with <10% from coaching after team setup. Indeed, the counter-measures to the 5 dysfunctions of a team are remarkably similar to the Scrum values. Daily Huddles and War Rooms tend to get facilitated by senior leaders. Lean & Agile can provide alignment , and the level autonomy depends on the level of servant leadership. Taken to the extreme, command & control with blame game is a good strategy to bring about the 5 dysfunctions of a team. I put it to you that the ideal for dealing with complexity 21st century is aligned autonomy, self-managing teams, and Team of Teams.
|
Scooped by
Mickael Ruau
August 7, 2020 8:41 AM
|
In this post we show you an alternative Scrum Framework poster and explain why we chose to present some of the Scrum elements differently.
|
Scooped by
Mickael Ruau
August 6, 2020 8:28 AM
|
Formations gratuites Formation gratuite: Les 14 plus grands référentiels du marché expliqués en 45 minutes Quel référentiel utiliser pour gérer efficacement ses projets? Un système d’information? Une architecture? La transformation de votre entreprise ? A l’issue de cette formation vous saurez discerner le deux principaux référentiels de gestion de projets (PMP®, PRINCE2®) parler des différences ... Read more
|
Scooped by
Mickael Ruau
August 3, 2020 2:24 AM
|
This detailed guide explains the key differences between Scrum and Kanban and helps leaders pick the right methodology and tools for their Agile teams.
|
Scooped by
Mickael Ruau
July 28, 2020 11:14 AM
|
|
Scooped by
Mickael Ruau
July 24, 2020 3:23 AM
|
Learn how the Cynefin Framework can help organizations select the right project management approach for their current reality.
|
Scooped by
Mickael Ruau
July 20, 2020 1:47 AM
|
My point is: why doing a big workshop to talk about all the roles and responsibilities in the team when what we actually want is to talk about the new people joining the team?
Can’t we just focus on the new people joining the team and get it done quickly?
However, in order to run some kind of expedite version of the workshop that focuses on some people you need a welcoming environment… An environment where it’s OK to talk openly about issues. A psychologically safe environment.
Which brings us to the real value of the workshop…
|
Scooped by
Mickael Ruau
July 16, 2020 1:11 PM
|
What are the different types of Scrum meetings and how to ensure your Scrum meetings are effective? Explore some Scrum best practices in our new blog post.
|
Scooped by
Mickael Ruau
July 16, 2020 1:00 PM
|
Définir un Sprint Goal ne sera pas naturel lors des premiers Sprints, un peu d’aide et direction peut être trouvée dans le modèle de Sprint Goal de Roman Pichler. Quels sont des exemples de Sprint Goal ? Sprint Goal Bon exemples Mauvais exemples Implémenter la fonctionnalité de recherche Comprendre si nous pouvons intégrer la solution Open Source XY au Produit Expérimenter l’utilisation d’une nouvelle technologie pour le rebranding de la fonctionnalité XY Corriger les anomalies #1234 and #3488 Implémenter la fonctionnalité de recherche et, si vous avez le temps, corriger les anomalies#3335 et#777 plus répondre à la question posée par le PDG lors de la dernière Sprint Review Réécrire la classe Java ShopProcess Conseils de lecture
The Professional Product Owner, Don McGreal and Ralph Jocham Agile Product Management With Scrum, Roman Pichler
Références
Le Scrum Guide fait référence au Sprint Goal 27 fois en 17 pages. Il est si important que chaque rôle, événement et artefact est, en quelque sorte, impacté par le Sprint Goal.
Le tableau suivant résume combien de fois le Sprint Goal est mentionné dans le Scrum Guide, dans quel paragraphe et dans quel but.
|
|
Scooped by
Mickael Ruau
September 22, 2020 6:02 AM
|
|
Scooped by
Mickael Ruau
August 26, 2020 10:36 AM
|
The Scrum Guide doesn't directly address how to incorporate scope changes into your Scrum implementation. As such, it is left up to the implementers to decide how to handle it. What I mean by scope changes is a material change to an existing Product Backlog Item(PBI), or an emergency last minute PBI. The strategy(chart) below…
|
Scooped by
Mickael Ruau
August 19, 2020 2:13 AM
|
Scrum presents you with a lot of opportunities to focus on such small, tiny improvements:
Every Daily Scrum is an infinitesimal step : to re-commit to the Sprint Goal, filter out the noise and keep the Development Team focused on the high priority work. It's a microscopic opportunity to re-plan and collaborate on " What's the most important thing we as a Development Team need to accomplish today"? In the Sprint Retrospective take that tiny step to slowly expand the Scrum Team's capabilities in-terms of : Definition Of Done, the engineering quality practices, limiting the work in progress, team collaboration, trust, transparency, shared accountability of work and team spirit. In the Sprint Review, take that minuscule step to tap into the stakeholders feedback, inspect the Done functionality and raise the transparency on the release progress and focus for the upcoming Sprint. In the Sprint Planning, take that baby step to create a meaningful Sprint Goal, that unites the Scrum Team with a singular objective. You won't get to one synergistic Sprint Goal the first time. That's okay, keep at it. Improve in the successive Sprints. Take that minimal step to spend time collaboratively as a Scrum Team to refine, review, re-order, discuss, decompose & delete the Product Backlog items during the Sprint, in every Sprint; consistently.
Don't miss these micro steps that Scrum offers. Latch on to them firmly. Commit to those small incremental improvements. Get them done in the Sprint.
These pave the way for the solid transformations like : valuable high quality Done Increments, maximizing the value delivery, better stakeholder engagement, responding to changing demand and enabling business agility!
|
Scooped by
Mickael Ruau
August 12, 2020 2:47 AM
|
Cet article est issu de mon livre “Scrum Insights for Practitioners”. J’ai écrit cet article parce-qu’il y avait un flou dans la compréhension de ce que signifient Transparence, Inspection et Adaptation dans le guide Scrum. J’ai souhaité apporter une explication simple des trois piliers de l’empirisme.
|
Scooped by
Mickael Ruau
August 7, 2020 11:08 AM
|
Peopleware: Productive Projects and Teams is a 1987 book on the social side of software development, specifically managing project teams. It was written by software consultants Tom DeMarco and Tim Lister, from their experience in the world of software development. This book was revised in 2013.
|
Scooped by
Mickael Ruau
August 7, 2020 7:06 AM
|
Téléchargez et imprimez (en A4 ou A3) le poster relatif à cet article, il pourra vous être utile au bureau, les QR codes permettent d'approfondir les sujets proposés ! Cet article fait partie d'une série de douze publications, chacune expliquant les bases de Scrum
|
Scooped by
Mickael Ruau
August 5, 2020 6:12 AM
|
Consider what organizational commitment means to you. What if everyone is committed to delivering value to the customers and not derailing the team?
|
Scooped by
Mickael Ruau
August 3, 2020 2:01 AM
|
Your global consulting partner for digital solutions that enable business transformation, create customer experiences and drive operational efficiency.
|
Scooped by
Mickael Ruau
July 27, 2020 2:18 AM
|
If the governance is in the Chaotic domain, do not think that using Scrum or any other Agile technique will solve your problems; what you will end up with is Acephalic Agile, as described by Andy Wilson’s post. You must solve management problems with management, not methodology.
Perhaps we can summarize this in the following table: Governance domain Disorder/ Chaotic Complex Complicated Simple Development domain Complex/ Complicated/ Simple Crisis management (of governance) Scrum Up-front planning Anything Disorder/ Chaotic Crisis management (of both code and governance) Crisis management (of code)
|
Scooped by
Mickael Ruau
July 22, 2020 5:37 AM
|
Dans son livre Adaptive Project Framework: Managing Complexity in the Face of Uncertainty, Robert Wysocki explique avoir observé qu’en ce début de 21e siècle, tout domaine confondu, environ 70% des projets nécessitaient une gestion de projet «adaptative» (tel qu’illustré dans la figure ci-bas). Le paysage de la gestion de projet Fig. 1 - Le paysage de la gestion de projet (R.Wysocki) (Traduction et adaptation par Claude Émond)
«Adaptative» est le mot qu’il utilise pour caractériser une approche «agile structurée» comme le Scrum, en opposition à une gestion de projet «extrême» ou l’agilité n’est plus structurée, mais plutôt improvisée, spontanée et réinventée constamment.
|
Scooped by
Mickael Ruau
July 17, 2020 4:22 AM
|
Scrum is definitely the basic and starting framework. But to succeed with agile, it works well when applied effectively with other agility practices.
Product/ project team should make a multi-faced approach to be agile. They can start agile transformation by following Scrum and then slowly moving to agile maturity with inspection & adaption, adapting suitable agile practices and investing in right tools & technologies.
|
Scooped by
Mickael Ruau
July 16, 2020 1:04 PM
|
An annotated guide to planning your sprints with GitHub issues.
|