This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The scrum methodology was developed as a response to rigid project management approaches such as the waterfall method, which didn’t adapt to the needs of agile product and software development teams. We’ll explore the scrum methodology in-depth, but before that, let’s start with a simple scrum definition. The Scrum Framework.
Everybody wants to Scale Scrum. So you have a couple of Scrum Teams that are working in adjacent areas and you're starting to face some challenges in delivering value in a coordinated integrative way. This is more or less the time you started searching for "scaling agile" "scaling scrum" and exploring your options.
Global Scrum Gathering. For the agile enthusiast, this scrum gathering takes place twice a year since 2013. There are presentations and interactive sessions led by experts that explore current implementation best practices and creative applications of agile and the scrum framework. May 11-13, New York, NY.
Scrum has been around for a while, they say. The Scrum Guide holds the definition of Scrum, they say. The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? What else happened along the road to the way that Scrum is defined and represented?
He asked me a question that if it was worth employing a Scrum Master. The question was, how do we create the career roadmap of a Scrum Master? My advice and viewpoint are as follows regarding the worthiness of the Scrum Master career path. . How can we determine the value of our work as a Scrum Master and Coach?
This is the essence of "self-management", and it is critical to Scrum teams and other kinds of Agile teams. Self-managing teams are central to Scrum and other Agile methodologies. High autonomy is an important contributor to successful Agile teams ( Donmez & Gudela, 2013 ; Tripp & Armstrong, 2018 ).
When people first look at the Scrum framework, they often see the roles and the events first. They see only the structure of Scrum; who wears the hats and when. But Scrum and the Agile methodologies it builds on are so much more. Scrum is a great example of a motivation framework. And that makes sense.
And we share results from our own analyses based on actual data from stakeholders and Scrum teams that we collected through the Scrum Team Survey. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. We collected the data through our Scrum Team Survey. We worked with Prof.
"There's no predictability/commitment in Agile/Scrum". They are either already victims of "Bad Scrum" or are basing their concerns off of a lot of "Bad Scrum" going on out there. Why didn't I just say "Agile/Scrum provides great predictability" and get it over with? See Chaos Report 2013 ). .
What the Scrum Guide says: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.” - K. Sutherland, Scrum Guide, 2013. Short Term: Scrum of Scrums.
Ever since the accidental creation of my book Scrum – A Pocket Guide (A Smart Travel Companion) in 2013, and its deliberate evolution in 2019, I frequently receive inquiries about the availability of an audiobook version. Starting Tuesday 24 March 2020 , I have planned a first series of five “ Daily Scrum Pocketcasts.”
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. From our own quantitative research with 1.200 Scrum Teams , we know that teams are more effective when they are more aware of the needs of their stakeholders. The Scrum Guide seems pretty clear about what Product Owners are accountable for.
In 2013 I wrote an article about the advantages and disadvantages of contract project managers. Competent agile coaches have been in high demand for many years due to the large number of companies across multiple industries who are going through agile transformations.
Por qué Scrum no tiene un evento de planificación de la Meta de Producto ? ¿Qué Y en la versión de 2013 se afirmaba que Scrum no prescribe ningún evento de planificación superior al Sprint. Video: como alinear Scrum y OKR En este video de 20 minutos explico como alinear ambos modelos a alto nivel.
Scrum has been around for a while, they say. The Scrum Guide holds the definition of Scrum, they say. The first, official version of the Scrum Guide was released in February 2010. So, how was Scrum defined before 2010 then? What else happened along the road to the way that Scrum is defined and represented?
Ever since the accidental creation of my book “ Scrum – A Pocket Guide ” in 2013, and its deliberate evolution in 2019, I’ve been receiving inquiries about an audiobook version. On Friday 27 March 2020 I delivered the fourth “ Daily Scrum Pocketcast ” in which I have read following chapters from my book: 2.7
Agile Manifesto Poster Scrum just turned 25 with a big celebration last November. Ward Cunningham (2013). This week marks another big milestone in the agile community, the 20th Anniversary of the Agile Manifesto. The weekend at the snowbird in Utah Feb 11-13, 2001 was exactly 20 years ago. Ron Jeffries (2018). Ken Schwaber (2015).
“Scrum” is a phenomenal subject – i.e. if you are familiar with it. As an Agile project manager, I have seen my fair share of so-called “Scrum Masters” and “Agile Experts” claiming to be masters of their craft. The truth, however, is that they don’t know a lot of things about Scrum and Agile. Introduction – Why Scrum?
In October 2003 my life of Scrum started, albeit not with Scrum. My life of Scrum actually started with eXtreme Programming which we then wrapped in Scrum. Fast forward >> In December 2010 I traveled to Zurich (Switzerland) to attend a PSM class (“Professional Scrum Master”) by Ken Schwaber.
Ever since the accidental creation of my book “ Scrum – A Pocket Guide ” in 2013, and its deliberate evolution in 2019, I’ve been receiving inquiries about an audiobook version. On Thursday 26 March 2020 I delivered the third “ Daily Scrum Pocketcast ” in which I have read following chapters from my book: 2.5
Apparently, it is easy to get stuck at interpreting the rules of Scrum. In the publication “ Moving Your Scrum Downfield ” I have described the six essential traits of the game to help you get unstuck and up your game. These six essential traits are indicative of Scrum coming to life. Every case of Scrum is unique.
Scrum cumplió 21 años en 2016. Desde 2011 ha habido dos grandes cambios en la guía de Scrum , en 2013 y 2016. Se reforzó el énfasis en el Daily Scrum como elemento de planificación -y no solamente sincronización- y también se cambió el nombre de la reunión de grooming a refinenement. Con muchos cambios.
Professional Scrum Trainers at the Face-to-Face Meeting #49 in Stuttgart, Germany (Photo Credit to Novatec) . My daughter, Bianca, was 8 months old when I started teaching Scrum (2013). See my post “ Finding Passion by Teaching Scrum ”). I entered the process of becoming a Professional Scrum Trainer (“PST”).
I hear people often talk about Scrum projects, but what does Scrum have to do with project management? In this article, I am not looking at Scrum from a software development perspective but rather from an organization-wide and project management perspective. In Scrum , we have three roles.
In my case, it largely boiled down to further increasing my independence as a Scrum Caretaker. Several members of the global movement of Scrum Caretakers helped me find direction and focus in two pilot sessions of the workshop I facilitated in February and March 2021. Gunther independent Scrum Caretaker. Warm regards.
Ryan is a Professional Scrum Trainer (PST) with Scrum.org. He hosts the Agile for Humans podcast and most recently co-wrote Fixing Your Scrum: Practical Solutions for Common Scrum Problems with Todd Miller for PragProg. Ryan is a Professional Scrum Trainer (PST) with Scrum.org. Today’s guest is Ryan Ripley.
During the Ebola outbreak 2013-2016, people exhibited anxiety-invoked behavior to a large extent. Scrum for example comes with two great assets in this situation: A Scrum Master, who also is a people-carer, and a Sprint Retrospective, which allows us to check in with everybody at least every couple of weeks. 2] Shultz, J.M.,
After a few years of searching and experimenting, “Scrum” was documented and presented to the general public. Scrum turns 25. I record a few highlights of “My life of Scrum”, a few aspects from the past 17 years of the life of an independent Scrum Caretaker. Later, we add Scrum to our approach.
Each post discusses scientific research that is relevant to our work with Scrum and Agile teams. 2013) actually suggests that code smells themselves are not necessarily the issue, but the length of the class being edited and the number of changes made to it over time. This post is part of our “in-depth” series. Why do software teams?
This article is the fourth in a series of “Kanban and Scrum – Stronger Together”. In the most recent post in Steve Porter’s series, Yuval Yuret presents Scrum in a manner that is intended to educate Kanban teams. Values shouldn’t be expressed as goals like they are in the Scrum Guide. Disclaimer.
I embarked on my Agile journey in 2003 when we wrapped eXtreme Programming in Scrum. Besides having engaged with many teams and organizations I have also created and facilitated many Scrum workshops and classes about various topics for various audiences since then. Warm regards Gunther independent Scrum Caretaker What?
See how approaches like the Scrum Framework and Liberating Structures can prevent some of these biases by bringing in diverse voices and by validating your assumptions against reality. For me personally, it's one of the reasons why I like the Scrum Framework , as it gives guide-rails to help us think and validate our assumptions with data.
While developing my book “ Scrum – A Pocket Guide ” (2013) I described how there is value in the Scrum Values. In 2016 the Scrum Values were added to the Scrum Guide. Find the slightly updated description of the Scrum Values as a separate section on this website. Scrum is a tool.
While developing my book “ Scrum – A Pocket Guide ” (2013) I described how there is value in the Scrum Values. In 2016 the Scrum Values were added to the Scrum Guide. Krystian previously created the Polish translation of the full text for the international Scrum Values PDF (September 2018).
Mijn boek Scrum Wegwijzer ( Een kompas voor de bewuste reiziger ) is de Nederlandse vertaling van mijn Engelstalige “smart travel companion” getiteld Scrum – A Pocket Guide. Scrum Wegwijzer 2e druk nu beschikbaar! Dat werd het Engelstalige Scrum – A Pocket Guide (A Smart Travel Companion). Gelukkig maar.
Ever since the accidental creation of my book “ Scrum – A Pocket Guide ” in 2013, and its deliberate evolution in 2019, I’ve been receiving inquiries about an audiobook version. In subsequent daily broadcasts I have read all chapters from my pocket guide to Scrum. THE FUTURE STATE OF SCRUM.
Ever since the accidental creation of my book “ Scrum – A Pocket Guide ” in 2013, and its deliberate evolution in 2019, I’ve been receiving inquiries about an audiobook version. In the subsequent daily broadcasts I will read the next chapters from my pocket guide to Scrum. THE AGILE PARADIGM.
Ever since the accidental creation of my book “ Scrum – A Pocket Guide ” in 2013, and its deliberate evolution in 2019, I’ve been receiving inquiries about an audiobook version. On Wednesday 25 March 2020 I delivered the second “ Daily Scrum Pocketcast ” in which I have read following chapters from my book: 1.6
The updated, third edition of my book “Scrum – A Pocket Guide” is now available worldwide, as a digital and as a paperback edition. I accidentally created the first edition of my book “Scrum – A Pocket Guide” in 2013. I consider how I described the Scrum Values in that first edition.
It is very similar to work engagement (Schaufeli & Salanova, 2014), which we also measure in both the Scrum Team Survey and TeamMetrics (as “team morale”). al, 2013), healthcare professionals (Papathanasiou et. 2013), and in the workplace (Manganelli, Thibault-Landry & Forest, 2018). Source: Wikipedia. . J., & Kee, Y.
In 2013 I accidentally created a book, “Scrum – A Pocket Guide” In 2018 I deliberately evolved my Scrum travel companion into a second edition. I am humbled over the many unanticipated consequences of the accidental creation of my pocket guide to Scrum. In July 2016 they were added to the Scrum Guide.
While developing my book “ Scrum – A Pocket Guide ” (2013) I described how there is value in the Scrum Values. In 2016 the Scrum Values were added to the Scrum Guide. I am gratified for sharing that: Konstantin Razumovsky from Proscrum.by (Belarus) created a Russian version of the Scrum Values.
At some point (I forgot when it was exactly), Léo Davesne approached me with the suggestion to create a French translation of my book “Scrum – A Pocket Guide” After the publication of the updated, 3rd edition of my book in English in early 2021, Léo started the actual translation of my words with the help of François Brunea.
En ocasiones se convierte en un arma arromadiza que los stakeholders, el Product Owner o incluso el Scrum Master utilizan para controlar el equipo. ¿Es Aunque los Stakeholders , el Product Owner o el Scrum Master puedan ver el Sprint Backlog, éste es propiedad del Equipo de Desarrollo. Es esta su función? Qué es el Sprint Backlog.
We organize all of the trending information in your field so you don't have to. Join 100,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content