Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

NOVEMBER 27, 2018

But many teams struggle with this rule. An increment is considered “Done” by the Development Team, but requires further testing and stabilization in the next Sprint. Or work is considered “Done” by the Development Team, but the install package still needs to be created. It is tempting to fall into “shades of Done”.

Software Review 185

Software Review SCRUM Technical Review Software 185

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 233

SCRUM Underperforming Technical Team Development Team Review 2020 233

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 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

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 194

Agile Underperforming Technical Team Estimate SCRUM 194

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 215

SCRUM Agile Technical Review Development Team Review 215

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? Or is this terra incognita?

ChatGPT 227

ChatGPT SCRUM Underperforming Technical Team Technical Review 227

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 246

Agile Software Review Technical Review SCRUM 246

Scrum.org

AUGUST 17, 2020

A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. Increased software quality can be demonstrated by measurably less technical debt, fewer bugs, and less time spent on maintenance.

SCRUM 234

SCRUM Technical Review Software Review Agile 234

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 211

SCRUM Underperforming Technical Team Software Review Development Team Review 211

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 220

SCRUM Development Team Review Technical Review Consulting 220

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

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. But unlike a traditional map, the landscape your product roadmap navigates is constantly shifting.

Development Team Review 148

Development Team Review 2022 Technical Review Software Review 148

Scrum.org

JUNE 23, 2019

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team is responsible for all estimates.

Development Team Review 177

Development Team Review Technical Review SCRUM Estimate 177

Scrum.org

JUNE 23, 2019

This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. The Development Team is responsible for all estimates.

Development Team Review 173

Development Team Review Technical Review SCRUM Estimate 173

Scrum.org

AUGUST 1, 2023

They commence their journey with clear intentions, understanding their role as value maximizers, focusing on delivering value, and diligently setting up their Product Backlog , goals, and stakeholder interactions. Validation: Regular assessment with stakeholders to ensure alignment. Vision: The overarching goal of the product.

Technical Review 172

Technical Review Development Team Review Transportation SCRUM 172

Planio

MAY 27, 2020

Without a clear definition of done , your development team doesn’t know what they’re working towards, your stakeholders are free to increase the scope, and your users most likely end up with a product that’s cluttered, confusing, and unusable. When can the development team change the definition of done (and how should they do it?).

Software Review 145

Software Review Technical Review Development Team Review Defining 145

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). You cannot scale crap - Scaling requires technical excellence.

Cadence 107

Cadence Technical Review Development Team Review Lean 107

Planio

DECEMBER 14, 2018

Sprints are the backbone of any good Agile development team. But maybe more than that, sprint planning aligns the development team with the product owner. Like any relationship, the one between you and your team requires communication and clarity. Step 1: Review your product roadmap. Download This Template.

Software Review 107

Software Review Planning Technical Review Development Team Review 107

Leading Answers

MARCH 7, 2019

When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable. Designing something is typically a consensus-gathering and problem-solving exercise. Here, traditional project management approaches work great.

Software Review 101

Software Review Technical Review Risk Management Software Development 101

nTask

NOVEMBER 12, 2018

They are considered to be an invaluable source of collecting information and feedback from the development team and help in keeping the team aligned with the Sprint goals. Sprint Review Meeting. Usually, the entire team is expected to be present during this meeting, including the product owner and the Scrum master.

SCRUM 123

SCRUM Development Team Review Technical Review 2018 123

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

Leading Agile

OCTOBER 10, 2018

In any enterprise that depends heavily on information systems, business agility is not possible without technical agility. Once a technology becomes part of the environment it tends to stay there, even after the shine wears off. I was showing their development teams how to automate functional tests using Cucumber.

Technical Review 96

Technical Review Software Review Underperforming Technical Team Engineering 96

Planio

APRIL 6, 2021

Master the delicate art of documentation in Agile and your team will thank you. The awkward truth is that 70% of projects fail due to a lack of requirement gathering. Yet despite this, too many teams think Agile is an excuse to build blindly. As an Agile team, you’re used to regularly shipping software.

Lean 78

Lean Technical Review Software Review Underperforming Technical Team 78

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.

2022 78

2022 Underperforming Technical Team Technical Review Development Team Review 78

Wrike

NOVEMBER 10, 2020

In the software and IT domain, a project manager ensures that a company’s technical projects are executed successfully. At the end of a workday, you’ll typically find project managers reviewing their day, rescheduling work that couldn’t happen, and reviewing their next day’s agenda.

Technical Review 74

Technical Review Software Review Construction Development Team Review 74

LiquidPlanner

MAY 15, 2018

Business teams struggled with understanding their role in a software project while trying to sort through all the technical jargon used to build a website. Related: Adopting Agile is an Exercise in Change Management. The business was also frustrated and doubted the team’s competency and ability to deliver. .

Agile 74

Agile Software Review Technical Review Development Team Review 74

Leading Answers

JUNE 14, 2018

Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development. Since they now represent the organization's f ace and communications vehicle, expect ongoing investment in their upkeep and technology refresh cycles.

Agile 116

Agile Technical Review Lean Sustainability 116

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

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 Government 78

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

Agilemania

NOVEMBER 11, 2022

Keep reading to find out more about this essential role in your company’s software development team. A Scrum Master is a facilitator who helps a Scrum team to self-organize, collaborate, and continuously improve. Facilitating daily stand-up meetings with the team. Providing feedback to the team.

SCRUM 88

SCRUM Certification Technical Review Lean 88

MPUG

JULY 15, 2019

If the developer or customer is unsure about a solution to a technical problem or estimation for a story, spike can be developed to answer these questions. Every development team uses a number of infrastructure related to coding, debugging, deployment, and configuration, among many others. Exercise on Stories.

Agile 99

Agile Software Review Infrastructure Estimate 99

Planio

AUGUST 1, 2022

For most development teams and startups, ‘becoming Agile’ starts and ends with how you build software. But a full Agile transformation isn’t just about the development process you use — it’s a way to bring creativity, innovation, and lean operations to every aspect of your business.

Agile 78

Agile Technical Review Leadership Infrastructure 78

Agilemania

MAY 25, 2022

Technical Debt . Boosts efficiency: Since prioritization of tasks happens regularly, the development team will be able to manage their time better. This boosts efficiency and improves productivity as it allows developers to spend the majority of their time developing rather than differentiating between items.

Underperforming Technical Team 52

Underperforming Technical Team Technical Review Development Team Review SCRUM 52

MPUG

JANUARY 23, 2023

Product Manager To understand the general scope of the work, we will review the generally regarded areas of expertise of the Product Manager and the Project Manager. Product Managers typically have a background in business, marketing, or engineering, and may work in various industries, including technology, consumer goods, and healthcare.

Manufacturing 59

Manufacturing Technical Review Engineering Defining 59

Leading Answers

JUNE 14, 2018

Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development. Since they now represent the organization's f ace and communications vehicle, expect ongoing investment in their upkeep and technology refresh cycles.

Agile 60

Agile Technical Review Lean Sustainability 60