Scrum.org

MARCH 19, 2023

models: The first experiment compares the Scrum Guide 2017 to the Scrum Guide 2020 The second experiment is designing a Retrospective exercise The third experiment is to help a new Scrum team to design a Definition of Done. Tell me: what is the difference between the Scrum Guide 2017 and the Scrum Guide 2020?

ChatGPT 144

ChatGPT SCRUM Technical Review 2020 144

Scrum.org

NOVEMBER 18, 2020

Wenn die Anleitungen im Scrum Guide von 2017 hilfreich für dich sind, dann verwende sie bitte auch weiterhin! . Ein Scrum Team ist ein Team. Das Development Team ist ein Grundpfeiler von Scrum. Trotzdem führt es häufig zu Verwirrungen: Warum ist das Development Team gleichzeitig eine Rolle und ein Team?

2020 233

2020 SCRUM 2017 Development Team Review 233

ProjectManager.com

NOVEMBER 22, 2021

A project management methodology is a set of principles, tools and techniques that are used to plan, execute and manage projects. Project management methodologies help project managers lead team members and manage work, while facilitating team collaboration. What Is a Project Management Methodology? Agile Methodology.

Technical Review 483

Technical Review Prince2 Manufacturing Lean 483

Scrum.org

NOVEMBER 18, 2020

The Sprint Review lost its detailed recipe on how to run the event. Interestingly, the authors also axed other elements of the 2017 edition of the Scrum Guide that I thought less contested, for example, the magnitude of work allocated to Product Backlog refinement and servant-leadership. Moreover, the “Why is this Sprint valuable?”

2020 180

2020 SCRUM Development Team Review Software Review 180

Planio

JANUARY 31, 2022

That’s why a product roadmap is the backbone of every great development team. Review and align your roadmap with other internal teams. A product roadmap is a visual representation of your short- and long-term priorities as a company that helps you plan, build consensus, and communicate high-level decisions.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Source : Scrum Guide 2017. The Product Backlog needs to represent at any given time the best use of the Development Team’s resources. Sprint Planning Anti-Patterns.

Development Team Review 185

Development Team Review Underperforming Technical Team SCRUM Technical Review 185

Planio

FEBRUARY 19, 2020

Free Test Plan Template. Based on our research on best test practives, we compiled a Test Plan Template for you to use for free. However, a 2017 study found that software failures cost the U.S. In short, you need a test plan. What is a test plan (and why do you need one)? Plan the test environment.

Planning 78

Planning Software Review Underperforming Technical Team Technical Review 78

Scrum.org

MARCH 18, 2020

Sprint Planning, Daily Scrum, Sprint Review & Sprint Retrospective . The Sprint Goal also provides guidance to the Development Team on why it is building the Increment. . . 2]: The Scrum Guide, Nov-2017 (accessed: 18-Mar-2020). Empiricism, Values & Trust . 1]: Scrum Framework Poster (accessed: 18-Mar-2020). [2]:

SCRUM 236

SCRUM 2020 2017 Development Team Review 236

Gunther Verheyen

FEBRUARY 27, 2024

Having no other plans for that time being, I could completely focus on my work as curator: contacting people, collecting ideas for essays, reviewing potential essays, suggesting potential edits, ordering and categorizing them, reviewing the manuscript and the cover. years before the deadline they had in mind). 1986, [link]. (2)

SCRUM 71

SCRUM 2004 Software Review 2019 71

Epicflow Blog

NOVEMBER 24, 2021

It can be represented as a series of the following phases: planning, design, development, testing, implementation, and maintenance of a product. SDLC has a clear structure of the whole development process, unchanged requirements, detailed documentation; requires careful planning, and is generally easy to manage. .

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Software Developers 98

Scrum.org

MAY 4, 2020

We had a look at common remote agile anti-patterns; we analyzed remote Retrospectives, Sprint Plannings as well as remote Sprint Reviews based on Liberating Structures. This eighth article now looks into supporting a distributed Development Team organizing a remote Daily Scrum. Source : Scrum Guide 2017.

SCRUM 161

SCRUM Agile Technical Review Development Team Review 161

Scrum.org

JUNE 18, 2021

What team cognition looks like for Scrum teams, and what signs tell you whether it's there or not. What research in this area tells us about how you can design, support, and encourage teams to develop team cognition and become high-performing. Pictures of a session where we created a skill matrix with a team.

2010 180

2010 SCRUM 2006 Software Review 180

Leading Answers

NOVEMBER 8, 2020

If the promotor had missed the M&Ms requirement, likely the whole setup needed to be thoroughly reviewed before testing. The nature of this work makes it problematic for upfront analysis and planning since many details continue to emerge throughout execution. It is often invisible, changing and less structured.

Agile 78

Agile 2020 Development Team Review Software Review 78

Scrum.org

NOVEMBER 28, 2020

The Scrum Guide is not updated frequently (the last update was 2017). What is important about Scrum is that it is a framework, and Scrum Teams need to define their process, practices, and tools within the framework. Another key change to the 2020 Scrum Guide is the shift from “Development Team” to “Developers.”.

2020 199

2020 SCRUM Underperforming Technical Team Software Review 199

Planio

JANUARY 17, 2022

In 2017, Apple did something no one expected. 9 steps to sunset a product, deprioritize a feature, and design a phase-out plan. Create a phase-out plan for features you’re going to remove (and deprioritize). Blindly following your roadmap or only revisiting it during an annual/quarterly planning session. scenarios.

Technical Review 109

Technical Review Software Review Development Team Review Underperforming Technical Team 109

Scrum.org

OCTOBER 24, 2018

I acted as the Scrum Master, and the band members made up the Development Team. The second album was released on July 28, 2017 and the band’s producer received the Independent Music Award for Best Music Producer. Our Definition of Done: vocals recorded for the music, and mixing and mastering finalized.

SCRUM 136

SCRUM Software Review 2017 2018 136

Velociteach

MAY 10, 2023

Everything from putting people back on the moon, developing new therapeutics and software, or planning a wedding. By the 6 th Edition (2017), it expanded to 49 processes organized into 10 knowledge areas and 5 process groups. Deming’s plan-do-check-act cycle is a prominent Lean practice. It also focuses on relationships.

Lean 89

Lean Cadence PMI 2001 89

Scrum.org

NOVEMBER 24, 2021

Release Master : The management and approval of plans to release new versions to stakeholders. Communicator : The transfer of knowledge between different sites, as well as from and to the team. Which activities can be fulfilled by others in the team, and what is needed for that? Insight #3: Product Discovery Is Missing?

2014 205

2014 2008 Technical Review 2019 205

Scrum.org

JUNE 16, 2022

The specific skills needed by the Developers are often broad and will vary with the domain of work. Außerdem genießen die Entwickler völlige Autonomie, was die technische Seite ihrer Arbeit angeht: For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done.

SCRUM 167

SCRUM Software Review Development Team Review 2020 167

Scrum.org

JANUARY 11, 2021

The Sprint Review lost its detailed recipe on how to run the event. Interestingly, the authors also axed other elements of the 2017 edition of the Scrum Guide that I thought less contested, for example, the magnitude of work allocated to Product Backlog refinement and servant-leadership. Commitment I: Product Goal.

SCRUM 123

SCRUM 2020 Development Team Review 2017 123

Scrum.org

NOVEMBER 25, 2019

The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. Source : Scrum Guide 2017. Sprint Retrospective Anti-Patterns of the Development Team. Sprint Retrospective Anti-Patterns.

Underperforming Technical Team 197

Underperforming Technical Team SCRUM Development Team Review Agile 197

Scrum.org

DECEMBER 19, 2019

In 2017 I was talking to the head of the Agile Coach Group of a large bank. They create Spreadsheets with questions/measures to assess how well these teams, groups and branches are complying with the standard way of working. too much re-planning and re-estimating wastes time and suffocates developers. .

SCRUM 123

SCRUM Development Team Review 2017 2019 123

Scrum.org

DECEMBER 17, 2018

Development Team Organises Its Own Work. The Development Team is both self-organising and cross-functional and by the end of each Sprint provides an increment that is ‘done’ and releasable. The team defines how to organise work in a Sprint. The Scrum Guide, 2017). No need to conduct a code review.

Software Review 109

Software Review Development Team Review 2017 2019 109

Scrum.org

DECEMBER 4, 2022

In many cases, managers play a critical role in providing guidance and support to teams, and in helping to create an environment that is conducive to using agile methodologies. It consists of a set of roles, meetings, and artifacts that help teams to work together and deliver value to their customers.

ChatGPT 170

ChatGPT Generative AI SCRUM Agile 170

Scrum.org

JULY 10, 2018

While working diligently behind feature flags, using elements of Scrum, it wasn’t clear to the stakeholders the value being delivered and how well the teams were progressing towards their end goal. Development teams are structured and empowered by the organisation to organise and manage their own work. Lessons learnt.

Technical Review 85

Technical Review Development Team Review Engineering 2017 85

Scrum.org

FEBRUARY 10, 2022

Deshalb habe ich bereits 2017 eine erste Umfrage zum Net Promoter Score® des Scaled Agile Framework SAFe ® durchgeführt. Bitte beachten Sie, dass ich Grammarly verwendet habe, um Tippfehler und Zeichensetzung zu korrigieren: While the cross-team big room planning is very useful, in my experience, SAFe is top-down.

Lean 166

Lean Software Review 2022 Technical Review 166

Wrike

FEBRUARY 22, 2024

7 basic task management tools Task management software helps you define and assign tasks, critical to both the planning and execution phases of any collaborative project. Hyper-efficient review, feedback, and approval features speed up processes. Say you’re part of a creative team designing marketing assets for a new product.

Software Review 36

Software Review Development Team Review Software Logistics 36

Scrum.org

FEBRUARY 7, 2022

Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. Please note that I used Grammarly to correct typos and punctuation: While the cross-team big room planning is very useful, in my experience, SAFe is top-down. TL; DR: The SAFe ® NPS ® Score as a Scaling Framework Is -56.

Lean 138

Lean Software Review 2022 Technical Review 138

Scrum.org

FEBRUARY 8, 2020

This was in late 2017. . I had various conversations and workshops with the development teams and the leadership. Each squad had a ‘Product Owner’ who were busy with understanding requirements, backlog management, coordinating between teams and team management tasks. . Output driven development.

Underperforming Technical Team 149

Underperforming Technical Team Software Review SCRUM Technical Review 149

Scrum.org

DECEMBER 4, 2019

The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team. Source : Scrum Guide 2017. See also the detailed lists of services rendered to the Product Owner, the Development Team, and the organization by the Scrum Master as defined by the Scrum Guide.). The Sprint Planning.

SCRUM 115

SCRUM Underperforming Technical Team Development Team Review Technical Review 115

Herding Cats

APRIL 16, 2019

Planning and Scheduling (#PS). Integrated Master Plan and Master Schedule (#IMPIMS). Product Development (#ProdDev). The following material comes from conferences, workshop, materials developed for clients. Without those, progress to plan can only be measured with the passage of time and consumption of money.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Gunther Verheyen

DECEMBER 22, 2017

Daily Scrum : a daily event, time-boxed to 15 minutes or less, to re-plan the development work during a Sprint. The event serves for the Development Team to share the daily progress, plan the work for the next 24 hours and update Sprint Backlog accordingly.

SCRUM 44

SCRUM Development Team Review 2013 2016 44

Scrum.org

NOVEMBER 2, 2018

When we started back in July 2017 it was a standard ‘task radiator’ borrowed straight from the boards at work: The columns on this were: Product Backlog, Sprint Backlog, In Progress, Needs Review (I think that was the first to go!), We still use planning poker numbers - so 1, 2, 3, 5, 8, 13, or 20. Done, and Established Systems.

SCRUM 123

SCRUM 2018 Underperforming Technical Team Software Review 123

International Institute for Learning

SEPTEMBER 20, 2022

For instance in the Agile Scrum Methodology [4] it is recommended to have 10 or fewer people in a team. Jeff Bezos, founder of Amazon, likes to use the “two-pizza rule” for strategy and development teams. If it takes more than two pizzas to feed (with a slice) the team, the team is likely too big.

Underperforming Technical Team 52

Underperforming Technical Team 2022 Technical Review 2002 52

Wrike

MARCH 14, 2023

Part of the Atlassian Group, Jira originated as bug tracking software for development teams , but has since grown to encompass a number of different products. Project management offices and teams: Juggling multiple projects? Create critical paths and dependencies, and drag and drop due dates as needed. What is Wrike?

Software Review 41

Software Review Technical Review 2006 Engineering 41

MPUG

JUNE 28, 2021

You may wish to use this transcript for the purposes of self-paced learning, searching for specific information, and/or performing a quick review of webinar content. What are the benefits of a requirements management plan? So, while this is in 2017, it might still be applicable to today. Hello, my name is Walter Stinnett.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52

Scrum.org

DECEMBER 17, 2018

Development Team Organises Its Own Work. The Development Team is both self-organising and cross-functional and by the end of each Sprint provides an increment that is ‘done’ and releasable. The team defines how to organise work in a Sprint. The Scrum Guide, 2017). No need to conduct a code review.

SCRUM 28

SCRUM Software Review Development Team Review 2017 28