Scrum.org

NOVEMBER 12, 2019

TL; DR: 15 Sprint Review Anti-Patterns. Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns. Are we still on the right track?

Development Team Review 142

Development Team Review Underperforming Technical Team SCRUM 2017 142

LiquidPlanner

JANUARY 16, 2018

Based on the classroom exercises, you’re excited to try new concepts and apply the magic cure-all that will solve all waterfall-based project problems. The development team should know what needs to be done, so just call the customer when it’s ready. Adopting Agile is an Exercise in Change Management.

Change Management 74

Change Management Agile Development Team Review Consulting 74

Rebel’s Guide to PM

MAY 12, 2020

Other teams hold their meetings around the Kanban board or whiteboard so everyone can refer to that if they need to. In Scrum, the development team attend the daily standup meeting. Agile team roles are quite specific, and yet, at the same time, you often find everyone mucking in to get the job done in a multi-skilled team.

SCRUM 352

SCRUM Agile Energy Development Team Review 352

Scrum.org

SEPTEMBER 13, 2018

Scrum.org says "PSM II is an advanced course helping students to understand the stances that characterise an effective Scrum Master and servant-leader while diving deep into how they serve the Development Team, Product Owner and organisation. How a Scrum Master services: The Development Team. Who Should Attend?

Development Team Review 108

Development Team Review SCRUM Leadership Agile 108

International Institute for Learning

JANUARY 25, 2023

Instead, you rely on the contributions and the support of the key stakeholders, the development team members, and possibly other product people who help you manage a large product. For example, the marketer has to create the marketing strategy, and the development teams have to design and build the product.

Development Team Review 52

Development Team Review Leadership Influencer SCRUM 52

Scrum.org

MARCH 22, 2021

The purpose of qualitative metrics is to gain insight into how one or more of an organization’s Scrum Teams are progressing with agile. The interval to test via self-assessment is every 4–12 weeks, with teams of lesser fluency running their tests at the lower end of this range. Question 44: First Steps of a New Scrum Team.

SCRUM 225

SCRUM Underperforming Technical Team Development Team Review Technical Review 225

Leading Answers

JUNE 22, 2022

Yet, in reality, some of the best leaders are quiet, introverted people who care deeply for their teams and stakeholders and quietly grind away toward a common goal. It can be learned and exercised on a small scale before being brought to bear on larger groups. This is another instance where having diversity on the team is helpful.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Energy 193

Scrum.org

SEPTEMBER 19, 2020

And now you’re trying to sell them that quitting this plan will turn out to be mutually beneficial—if they trust the product development entity’s ambition to develop into an agile, learning, customer-centric organization. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team.

Technical Review 188

Technical Review Software Review Development Team Review Cadence 188

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. Ask past users for reviews. Roadmaps are an exercise in prioritization. Roadmaps establish trust between you and your development team.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Scrum.org

OCTOBER 30, 2020

Instead of trying to figure out an answer within your team, explore it together with stakeholders. We’ve successfully used this exercise with virtual teams. The Daily Scrum is where the Development Team plans their collaboration towards achieving the Sprint Goal for the next 24 hours. Sprint Review.

Technical Review 211

Technical Review SCRUM Development Team Review Consulting 211

Scrum.org

SEPTEMBER 13, 2021

Scrum Anti-Patterns: From Product Backlog to Sprint Review. I added new questions on Scrum anti-patterns, from the Product Backlog to the Sprint Planning to the Sprint Review, to provide more insight into the Scrum value creation process and the organization’s return on investment. Question 45: Scrum Master Anti-Patterns.

SCRUM 201

SCRUM Underperforming Technical Team Development Team Review 2020 201

Scrum.org

OCTOBER 7, 2019

TL; DR: Faking Agile Metrics — An Eye-Opening Exercise. Imagine you’re a Scrum Master and the line manager of your team believes that the best sign for a successful agile transformation is a steady increase in the Scrum Team’s velocity. Moreover, if the team fails to deliver on that metric something is wrong with the Scrum Team.

Agile 169

Agile Underperforming Technical Team Estimate SCRUM 169

Scrum.org

FEBRUARY 25, 2024

Reassigning Team Members : Frequently moving team members between Scrum Teams disrupts the building of trust and undermines the stability and effectiveness of teams​​. In the absence of this feedback, teams may engage in gold-plating under the assumption that they are adding value.

SCRUM 178

SCRUM ChatGPT Technical Review Development Team Review 178

NimbleWork

MAY 1, 2024

In a software development project, email notifications, team meetings, and code reviews can be represented using symbols to visualize the communication and collaboration process. In this example, we will consider a software development team working on a web application for an e-commerce platform. Source: Medium 2.

Software Review 52

Software Review Process Technical Review Development Team Review 52

Scrum.org

DECEMBER 7, 2022

Consider a cadence that involves Planning, Reviewing, and Retrospecting with a clear distinction between the team working on the OKR and its stakeholders. . After identifying the few real OKRs, assess who’s needed to work towards each of them. The Scrum framework provides one example of how such a cadence could look.

Cadence 184

Cadence Development Team Review Initiating SCRUM 184

Scrum.org

SEPTEMBER 8, 2020

Using the budgeting process as a Stage-Gate® to exercise control through the back door : The budgeting process is hard to align with agile requirements like the longevity of teams. Instead, the management ought to provide the teams with goals and guidance on how to achieve these, along with funding sufficient to meet the objectives.

Software Review 191

Software Review Agile Underperforming Technical Team Development Team Review 191

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. The Product Owner and Scrum Master are now considered equal members of the Scrum Team.

ChatGPT 146

ChatGPT SCRUM Technical Review 2020 146

Planio

AUGUST 1, 2023

6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. A successful strategy isn’t a set-and-forget exercise. A successful strategy isn’t a set-and-forget exercise.

Development Team Review 78

Development Team Review Infrastructure Software Review Governance 78

Scrum.org

MARCH 2, 2020

Any of the examples will impede the team’s productivity and might endanger the Sprint goal. The Scrum Master must prevent them from manifesting themselves: The Scrum Master has a laissez-faire policy as far as access to the Development team is concerned. Remember: Product Backlog item creation is a Scrum Team exercise.).

SCRUM 213

SCRUM Development Team Review Underperforming Technical Team Technical Review 213

Scrum.org

FEBRUARY 4, 2020

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Remember: user story creation is a team exercise.). To a certain extent, it is also a negotiation between the Product Owner and the Development Team. Source : Scrum Guide 2017.

Development Team Review 191

Development Team Review Underperforming Technical Team SCRUM Technical Review 191

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. When a weak Development Team meets a commanding Product Owner, focusing on shipping new features, the team may end up as a feature factory, churning out new code while neglecting the technical foundation.

SCRUM 226

SCRUM Underperforming Technical Team Technical Review Software Review 226

Scrum.org

JANUARY 9, 2023

Follow-up question : Why is it beneficial that the team adheres to the values and practices of Scrum? This can help improve the overall quality of the team's work and ensure that the team is meeting its goals. Question : Should a Scrum Master remove problems on behalf of the Scrum Team?

ChatGPT 218

ChatGPT SCRUM Underperforming Technical Team Technical Review 218

Scrum.org

AUGUST 1, 2023

Validation: Regular assessment with stakeholders to ensure alignment. Diagram from Scrum.org PSPO course Visualizing the Dilemma: A Product Owner's Scenario Consider a bank scenario - A customer applies for a mortgage, and the bank provides various services like KYC verification, Credit Assessment, Loan Underwriters, etc.

Technical Review 140

Technical Review Development Team Review Transportation SCRUM 140

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. Do you want to get this article in your inbox?

SCRUM 167

SCRUM Agile Technical Review Development Team Review 167

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. When stress remains present for a longer period of time, what strategies do you have individually and as a team to cope with it?

Sustainability 176

Sustainability 2015 2014 2013 176

Project Pulse Journal

APRIL 16, 2024

Let us now check the world of T-shirt sizing - one of the project management tools that promises to streamline your planning process and transform it into an engaging, team-building exercise. Review and Adjust - Once all items are sized, review the assignments to ensure consistency across the backlog.

Agile 52

Agile Technical Review Software Review Development Team Review 52

Techno-PM

MARCH 15, 2022

The training includes everything from hands-on exercises to lectures to prepare participants well when they take the exam at the end of the course. They are responsible for ensuring that all team members adhere to the agreed-upon processes and procedures and remove any impediments that might be slowing down progress.

SCRUM 68

SCRUM Agile Technical Review Software Review 68

Planio

MARCH 27, 2023

Unfortunately, too many project managers and development teams are eager to build and skip the stakeholder analysis stage. Stakeholder analysis involves identifying the people associated with your project, grouping them, assessing their needs, and planning how to manage them. Lessons learned review. Org chart review.

Planning 78

Planning Development Team Review Influencer Initiating 78

Scrum.org

OCTOBER 19, 2020

Daily Scrums are an important part of Scrum, but not all Daily Scrums need to be formal — a Development Team should not have a Daily Scrum for the sake of having it; it serves a different purpose than ticking off a box on a checklist. A small, experienced, and co-located team may use a morning coffee break for their Daily Scrum.

SCRUM 161

SCRUM Underperforming Technical Team Software Review Development Team Review 161

Scrum.org

NOVEMBER 25, 2019

No matter the frequency of your retrospectives you should always watch out for the following Sprint Retrospective anti-patterns from the Scrum Team, the Development Team, the Scrum Master, as well as the organization: Sprint Retrospective Anti-Patterns of the Scrum Team. Sprint Retrospective Anti-Patterns.

Underperforming Technical Team 199

Underperforming Technical Team SCRUM Development Team Review Agile 199

Scrum.org

JANUARY 14, 2021

Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). No team-level Sprint Review.

Cadence 137

Cadence Technical Review Development Team Review Lean 137

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 181

2010 SCRUM 2006 Software Review 181

PM Basics

OCTOBER 2, 2018

My development Team Lead – John. Here you will need to exercise the ability to analyze the feedback. Moreover, you can assess the openness of stakeholders to the idea you research. In project management, you never use a tool or a technique as is. First of all, I decided on whom should I ask. Advantages You can Gain.

Development Team Review 189

Development Team Review Risk Management Risk Estimate 189

Scrum.org

MAY 5, 2020

Due to the COVID-19 crisis, chances are that everyone in your organization is working from home. This includes your Product Owner and Development Team. Start a “Scrum Question of the Week” exercise. At the start of the week, you offer the team a question about the Scrum theory & principles. Things to try….

SCRUM 172

SCRUM Development Team Review Technical Review Consulting 172

Scrum.org

FEBRUARY 9, 2022

Business stakeholders meet regularly with the agile team at a lower level of engagement. In Scrum, this engagement may take place in refinement meetings or at the Sprint Review. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Conclusion.

Agile 245

Agile Software Review Technical Review SCRUM 245

nTask

DECEMBER 21, 2021

This backlog contains many different elements like enhancements, bug fixes that the development team has to perform, new features that have to be introduced, and the technology upgrades that are needed in the current product. Let’s take a look at the core principles of the product backlog management process. Product Backlog Grooming.

2022 78

2022 Underperforming Technical Team Technical Review Development Team Review 78

Scrum.org

SEPTEMBER 27, 2021

This latest update to the interview guide addresses Product Owner anti-patterns from Product Backlog management and refinement to the Sprint Review. Remember: Product Backlog item creation is a team exercise in most cases.). Sprint Review Anti-Patterns. Remember the old saying: There is no “I” in “team?”).

Underperforming Technical Team 187

Underperforming Technical Team SCRUM Technical Review Development Team Review 187