Scrum.org

NOVEMBER 15, 2022

Now coming to the 3rd expectation which is the ‘HOW’ of sprint planning, the Developers and only developers are expected to plan the work necessary to create an increment that meets the definition of Done. What does that mean and how much to do, is what I plan to discuss in this blog. Code Review. Peer Review.

Planning 117

Planning Software Review Development Team Review 2017 117

Planio

JANUARY 17, 2022

In 2017, Apple did something no one expected. Support metrics: Is it taking time away from your support and development teams? For example, you might set aside time each quarter to review decisions or look at feature performance during a sprint retrospective. Respect your team the same way you respect your customers.

Technical Review 109

Technical Review Software Review Development Team Review Underperforming Technical Team 109

Scrum.org

AUGUST 25, 2022

This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. This increases blood pressure, heart rate, and tenses muscles (McEwen, 2017). Burnout–depression overlap: A review.

Sustainability 178

Sustainability 2015 2014 2013 178

Project Pulse Journal

APRIL 17, 2024

From individual coding tasks to large-scale releases, the DoD sets the bar for quality and completeness, ensuring everyone - from developers to stakeholders - is on the same page. This article will help you craft a robust DoD that suits your project needs and team dynamics. Ready to transform your project delivery process?

Software Review 52

Software Review Development Team Review Technical Review 2024 52

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.

2020 182

2020 SCRUM Development Team Review Software Review 182

Scrum.org

JUNE 18, 2021

you know how that feels. We’re talking about those moments of crisis where the team is faced with a demanding challenge, and everyone just seems to intuitively know how to act and constructively add to each other's contributions. It's almost like the team has a “mind” of its own. What does this mean for your Scrum Team?

2010 182

2010 SCRUM 2006 Software Review 182

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. To a certain extent, it is also a negotiation between the Product Owner and the Development Team. A serious goal answers the “What are we fighting for?”

Development Team Review 193

Development Team Review Underperforming Technical Team SCRUM Technical Review 193

ProjectManager.com

NOVEMBER 22, 2021

The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. It became a part of agile when Ken Schwaber and Mike Beedle wrote the book “Agile Software Development with Scrum” in 2001. Get work management software that fits with every methodology.

Technical Review 483

Technical Review Prince2 Manufacturing Lean 483

Scrum.org

MAY 4, 2020

We started this series on remote agile with looking into practices and tools; we explored virtual Liberating Structures, and how to master Zoom. 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.

SCRUM 169

SCRUM Agile Technical Review Development Team Review 169

Scrum.org

NOVEMBER 24, 2021

How to use these insights in practice. Which activities can be fulfilled by others in the team, and what is needed for that? One of the reviewers of this article, Maarten Dalmijn , noted that he missed “product discovery” as a core activity in the work by Bass (2018). Data from our Scrum Team Survey may shed a light on this.

2014 211

2014 2008 Technical Review 2019 211

Leading Answers

NOVEMBER 8, 2020

However, it is when we start discussing the “how-to” path for achieving these goals that passionate debate occurs. If the promotor had missed the M&Ms requirement, likely the whole setup needed to be thoroughly reviewed before testing. Everybody is trying to get to the same destination of successful outcomes and happy stakeholders.

Agile 78

Agile 2020 Development Team Review Software Review 78

Scrum.org

MARCH 31, 2020

Despite the rapidness of the change, moving to remote worked surprisingly well for many teams, because they were used to some degree of remote work before. Especially development teams and technology firms in general have many years of experience with allowing their workforce to do their jobs from wherever and whenever they like.

Underperforming Technical Team 153

Underperforming Technical Team 2020 Technical Review 2016 153

Scrum.org

DECEMBER 19, 2019

In 2017 I was talking to the head of the Agile Coach Group of a large bank. I asked her how she would know that her method would work in other contexts as well? They create Spreadsheets with questions/measures to assess how well these teams, groups and branches are complying with the standard way of working.

SCRUM 126

SCRUM Development Team Review 2017 2019 126

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 115

Software Review Development Team Review 2017 2019 115

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. By the way, it’s free.

SCRUM 129

SCRUM 2020 Development Team Review 2017 129

Scrum.org

JUNE 16, 2022

How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value. Im Vergleich zu diesem Dopamin-Fix ist es weniger befriedigend im Code Review zu prüfen, wie ein anderes Teammitglied ein anderes Problem gelöst hat.

SCRUM 175

SCRUM Software Review Development Team Review 2020 175

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.

Technical Review 86

Technical Review Development Team Review Engineering 2017 86

Scrum.org

DECEMBER 4, 2022

It consists of a set of roles, meetings, and artifacts that help teams to work together and deliver value to their customers. The key roles in Scrum include the Scrum Master, the Product Owner, and the development team. The suggestion is a correct, universal answer to the question of how to bring about change.

ChatGPT 179

ChatGPT Generative AI SCRUM Agile 179

Scrum.org

FEBRUARY 10, 2022

Deshalb habe ich bereits 2017 eine erste Umfrage zum Net Promoter Score® des Scaled Agile Framework SAFe ® durchgeführt. And then SAFe dropped “Customer Centricity” and “Design Thinking” on their infographics, but they still have no idea what these mean or how to do them well. Das Ergebnis war damals -52. This has value for me.

Lean 175

Lean Software Review 2022 Technical Review 175

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®. And then SAFe dropped “Customer Centricity” and “Design Thinking” on their infographics, but they still have no idea what these mean or how to do them well. TL; DR: The SAFe ® NPS ® Score as a Scaling Framework Is -56.

Lean 144

Lean Software Review 2022 Technical Review 144

Wrike

FEBRUARY 22, 2024

Hyper-efficient review, feedback, and approval features speed up processes. Alongside team dashboards, everyone gets a personal dashboard they can use to check their upcoming tasks, watch progress on other tasks that affect their work, and check their latest notifications (e.g., Customer reviews Wrike is rated 4.3

Software Review 36

Software Review Development Team Review Software Logistics 36

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 118

SCRUM Underperforming Technical Team Development Team Review Technical Review 118

Scrum.org

FEBRUARY 8, 2020

How to bring all of this together? This was in late 2017. . I had various conversations and workshops with the development teams and the leadership. With all this information I created an understanding about how the work works over time, and used that systemic understanding to make the following recommendations.

Underperforming Technical Team 154

Underperforming Technical Team Software Review SCRUM Technical Review 154

Binfire

FEBRUARY 22, 2017

This is not a product review article, but a guide on how to choose the right software for your needs. There are hundreds of comparison sites which write articles like “The 10 best project management software for 2017” or “Top 25 project management software” etc. Teams with less than 500 members.

Software Review 119

Software Review Software Aerospace Development Team Review 119

Herding Cats

APRIL 16, 2019

The following material comes from conferences, workshop, materials developed for clients. The overarching theme is focused on defining what Done looks like, assessing progress toward Done in units of measure meaningful to the decision makers. Here are presentations and paper on how to do that in a variety of domains. .

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Planio

FEBRUARY 19, 2020

However, a 2017 study found that software failures cost the U.S. How deep do you really need to go to ensure your product holds up and your users get what they expect? How do you know when to resume a paused test? What are the steps for reviewing what’s been done and picking up? Download Free Template. economy $1.7

Planning 78

Planning Software Review Underperforming Technical Team Technical Review 78

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!), How many sprints have you done? We started in July 2017, so we’re well over a year in now.

SCRUM 126

SCRUM 2018 Underperforming Technical Team Software Review 126

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. You can also access a wide range of resources such as webinars , community discussions , and how-to guides to help you on your journey.

Software Review 41

Software Review Technical Review 2006 Engineering 41

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

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. And in this particular year, which was 2017, they found that 47% of unsuccessful projects failed to meet original goals due to poor requirements.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Defining Project Life Cycle 52