Scrum.org

APRIL 17, 2025

Vision and Ideation: AI as a Creative Partner The product vision is the cornerstone of successful product development. For example, imagine a product owner for a meal-planning application using an AI tool to analyse thousands of customer reviews and support conversations.

Software Review 109

Software Review SCRUM Artificial Inteligence Technical Review 109

Scrum.org

APRIL 1, 2022

Long has spoonfeeding solutions and off-the-shelf feature descriptions prevailed in many development teams. Although some issues might have been fixed, I rarely see the full potential of a Scrum Team being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.

Underperforming Technical Team 227

Underperforming Technical Team SCRUM Innovation Leadership 227

The IIL Blog

JULY 31, 2024

By Debra Khan Practitioners of content strategy do not have to go it alone when developing a strategy for a content project. Based on the needs analysis, project leadership typically develops a business case and charters a project. I like to do assessments from time to time, beyond the regular meetings and updates.

Technical Review 88

Technical Review Development Team Review 2013 Underperforming Technical Team 88

Scrum.org

JULY 10, 2018

Often I hear people say that Scrum does not take care of risk: there is no risk log, risk is not on the agenda of the Sprint Review or Retrospective as a standard agenda-item. The Development Teams need to be accountable for the quality of the product and how it's made. That's a risk right there!

Risk Management 149

Risk Management Risk Technical Review Underperforming Technical Team 149

Scrum.org

OCTOBER 28, 2022

Long has spoon-feeding solutions and off-the-shelf feature descriptions prevailed in many development teams. Although some issues might have been fixed, I rarely see the full potential of a Scrum Team being achieved. Going all-in on predefined features fails to capitalize on hidden ideas in the brains of team members.

Underperforming Technical Team 202

Underperforming Technical Team SCRUM Innovation Leadership 202

nTask

DECEMBER 8, 2020

These qualifications have evolved due to the challenges that are faced by the companies in the project management paradigm – and that too on daily basis. They will help improve the communication channels that are present in the company, resulting in improved communication and collaboration between the team leaders and project managers.

Underperforming Technical Team 158

Underperforming Technical Team Planning Development Team Review Software Review 158

Leading Answers

JANUARY 16, 2021

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. What is a Risk-Adjusted Backlog? A risk-adjusted backlog is a backlog that contains activities relating to managing risk in addition to the usual features associated with delivering value.

Risk 145

Risk 2006 Underperforming Technical Team 2012 145

Scrum.org

NOVEMBER 22, 2019

The Project Manager is typically concerned with day-to-day progress of the Development Team. They rarely (or never) miss a Daily Scrum, they’re involved during the Daily Scrum and it might just be that they’re asking individual team members what they’ve done, what they’re going to do and if there’s anything blocking them.

Underperforming Technical Team 109

Underperforming Technical Team Development Team Review Government Governance 109

The IIL Blog

DECEMBER 11, 2024

The bad news is that this complicates the decision on which to choose. Clear Deadlines and Roles Each team member’s deadlines are listed clearly next to their tasks and they can see how those deadlines impact others’ deadlines [3]. It also makes it easier for the team to understand their tasks [4].

Artificial Inteligence 78

Artificial Inteligence Leadership Software Review 2024 78

Scrum.org

MARCH 2, 2020

Too bad, when nowadays diversity, autonomy, mastery, and purpose become the driving factors in a highly competitive environment where more of the same for everyone is no longer creating value. Flow disruption: The Scrum Master allows stakeholders to disrupt the flow of the Scrum Team during the Sprint. The Sprint. Nice try #1.).

SCRUM 243

SCRUM Development Team Review Underperforming Technical Team Technical Review 243

Scrum.org

SEPTEMBER 19, 2020

It's a key inspect and adapt opportunity for the Development Team, encouraging them check their progress towards the Sprint Goal and adjust their plan accordingly. It's also supposed to be an event for the Development Team and run by the Development Team but as we know in "the real world" it's not always implemented that way!

SCRUM 226

SCRUM Underperforming Technical Team Development Team Review Technical Review 226

Scrum.org

MARCH 11, 2023

Why do we deliver poor quality? From a bigger perspective these are all different risks. Technical risks or business risks or risks in general. What I’ve found interesting is how we deal with risks. The tool: Product Opportunity Assessment (POA): What problem will this solve? Can the user use it?

Underperforming Technical Team 195

Underperforming Technical Team Development Team Review Risk Management Risk 195

Scrum.org

OCTOBER 12, 2020

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. As somebody hiring for a Scrum Team, you need to determine for yourself what works for your organization — which is a process, not a destination. Generally, insisting that the team achieve specific KPI, e.

SCRUM 234

SCRUM Underperforming Technical Team Technical Review Software Review 234

Scrum.org

JULY 21, 2020

Regularly, we find articles from developers detailing why ‘Agile’ in general and Scrum’s nature, in particular, deserve our collective disdain. These rigid methodologies inevitably turn developers into mindless cogs in a corporate machinery—churning out more and more code—while ignoring the true potential of these knowledge workers.

Software Review 224

Software Review Underperforming Technical Team SCRUM Engineering 224

Scrum.org

APRIL 7, 2022

Recently, the concept of “fluid teams”, “dynamic reteaming” or “ad-hoc teaming” has gained traction in the Agile community. Although the concept has many different definitions, a characteristic they share is that members move in and out of a team during its lifetime. The need for fluid teams.

Underperforming Technical Team 202

Underperforming Technical Team 2007 2006 2009 202

Scrum.org

APRIL 10, 2019

Are we really a Team? . Looking back a couple of years ago, I had a chance to work with the great team. They are a great team, but not from the beginning.that was a broken team when I came. - The team used Scrum but the Transparency was lost. Development Team hid issues from Product Owner when he came to ask.

SCRUM 184

SCRUM Underperforming Technical Team Development Team Review Software Review 184

Scrum.org

SEPTEMBER 4, 2019

In this blog post, I’ll explain how it’s possible for managers to work with Scrum Teams so no one has to worry about rebuilding their resume. Scrum is a framework designed to get complex products to market while mitigating the risk associated with building them. The kind of manager that unifies the team.

Underperforming Technical Team 169

Underperforming Technical Team SCRUM Software Review Technical Review 169

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 181

Software Review SCRUM Technical Review Software 181

Leading Answers

JUNE 22, 2022

This is part one in a series on leading agile teams from the Beyond Agile book. We will examine what leadership entails and how it applies to agile teams. We can create backlogs and release plans all we like, but until there is a motivated team with a shared vision of the end goal, it is like trying to push a rope—ineffective.

Leadership 193

Leadership Underperforming Technical Team Development Team Review Lean 193

Scrum.org

JANUARY 29, 2024

( Japanese version・日本語版 ) When picturing an effective and truly agile product development team, one often imagines a software development team, pushing some software to production every day, maybe multiple times a day, ala Amazon. The problem with this way of thinking is that risk builds up over time.

Agile 208

Agile Technical Review Underperforming Technical Team Development Team Review 208

Scrum.org

JANUARY 9, 2020

I am actively forming the opinion that this is the wrong term to be used both in how various assessments assess understanding and by practitioners in the agile community. This poor choice then leads to a fragility within the solution. The Scrum Guide does not contain the term technical debt. Lean Principles Work Types.

Underperforming Technical Team 154

Underperforming Technical Team Infrastructure Development Team Review Lean 154

Project Bliss

OCTOBER 3, 2017

Projects stay interesting with new challenges, opportunities to collaborate with teams, and the satisfaction of delivering value and solutions. You need to understand risk and finances, and evaluate projects based on ROI. Therefore, the program manager will be interacting with multiple project managers and multiple project teams.

Underperforming Technical Team 237

Underperforming Technical Team PMO Finance Executing 237

Alan Parker Blog

AUGUST 16, 2024

This section of Annex A addresses the risks associated with user endpoint devices, network security, software development, and information systems management, ensuring that organisations can effectively defend against ever-evolving cyber threats.

Technical Review 52

Technical Review Controlling Software Review Development Team Review 52

Scrum.org

NOVEMBER 28, 2020

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. I have worked with many Scrum Teams who have been using the concept of mid-term and longer-term goals as part of their Product Backlog management strategies. Scrum is still Scrum. Absolutely!

2020 222

2020 SCRUM Underperforming Technical Team Software Review 222

The IIL Blog

OCTOBER 17, 2023

Whether you are just starting out, developing your project manager resume, or a seasoned professional, mastering the Project Management Buzzwords is non-negotiable. Agile team A cross-functional group of individuals (e.g., Business case An organization will develop a document to justify the investment in a project (i.e.,

Development Team Review 148

Development Team Review Project Life Cycle Underperforming Technical Team Estimate 148

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 201

Underperforming Technical Team 2020 2016 Technical Review 201

ProjectManager.com

MAY 5, 2022

When working in an agile environment, teams take sprints, a short period of time in which you complete tasks. Scrum teams choose this work by looking over their backlog. A scrum framework allows teams to execute in agile project management, the backlog is very important and backlog refinement keeps work flowing. Learn More!

Underperforming Technical Team 221

Underperforming Technical Team SCRUM Estimate Development Team Review 221

Scrum.org

DECEMBER 6, 2019

With Scrum you have one and only one product owner for a given product – not a committee, but the effectiveness of the product owner will vary depending on the PO’s organizational enablement, understanding of the product, and involvement with the Scrum team. . . An Evaluation Matrix. Quadrant Q2: PO as Constrained SME. PO Availability.

Underperforming Technical Team 158

Underperforming Technical Team Development Team Review SCRUM Risk 158

Leading Answers

NOVEMBER 1, 2020

So, the responsible thing to do is to agree upfront on how everyone will be kept informed of the project’s progress, risks, issues, etc. Demos  – Having the team demonstrate increments of functionality at the end of every iteration shows what the project has achieved to date. Let’s examine a few….

Agile 135

Agile Planning Underperforming Technical Team Development Team Review 135

Scrum.org

MARCH 18, 2020

Work (or sometimes even a transformation) is ongoing, and the organization wants a second opinion on risk or improvement factors. . A new product had been developed to replace an older, third party solution that was no longer tenable. First off, it’s important to note that bureaucracy isn’t bad. And now in these four articles.

Technical Review 179

Technical Review Underperforming Technical Team Software Review Development Team Review 179

nTask

OCTOBER 14, 2021

Risk management is a crucial element to keep track of when it comes to any sort of project. But when it comes to construction risk management, you need to be extra careful, because a software project going bad might not be as life-threatening as a construction project going bad. What is Construction Risk Management?

Construction 78

Construction 2021 Risk Management Risk 78

Project Bliss

MAY 24, 2017

When you finish reading this post, you’ll have a better understanding of each, what each looks like when applied to a simple project, and reasons why each might be good or bad approaches for your team. The team repeats the same steps over and over. The team also reassess the work as they develop the solution.

Agile 185

Agile Software Review Underperforming Technical Team Technical Review 185

Inloox

APRIL 16, 2024

How to perform a SWOT analysis Once the SWOT analysis is completed: 5 key approaches for strategy development Concrete example: SWOT analysis in a software development project Conclusion 1. Understanding these strengths allows the project team to target them in order to maximize the project's chances of success.

Artificial Inteligence 100

Artificial Inteligence Underperforming Technical Team Technical Review Development Team Review 100

Scrum.org

FEBRUARY 8, 2020

Our Business Lending product is being developed by more than 20 teams spread across 3 sites. Each team contains business, IT and operations skills. Previously, I was involved in setting up a retail bank from scratch and in the development of mortgages solutions. My talk was about programmers in large scale development.

Underperforming Technical Team 195

Underperforming Technical Team Software Review SCRUM Technical Review 195

Scrum.org

APRIL 8, 2019

Today’s biggest impediment and cost to agility is the impact of teams waiting for decisions. I see numerous product development teams carrying unfinished work sprint over sprint because they are delayed waiting on decisions for direction, funding, or getting expenses approved for equipment. Money talks. Watch my video below.

Underperforming Technical Team 135

Underperforming Technical Team Development Team Review Influencer Controlling 135

nTask

FEBRUARY 23, 2022

In the way of organizational success, there lies a noteworthy foe that is ever-present and makes sure that you and your goals are berated and questioned at every step of the project development process. This “foe” is the stakeholders’ approvals and reviews. Not to make it sound too comical, but the general idea is the same.

2022 97

2022 Underperforming Technical Team Development Team Review Risk Management 97

Scrum.org

MARCH 4, 2019

Newly trained Agilists typically are assigned to join an existing project team by means of an experiment. Most people in the team are unhappy and try to switch projects, but not the Scrum Master. However, we discover that predictive planning is much like gambling and that empiricism could bring more opportunities for mitigating risk.

SCRUM 153

SCRUM Software Review Development Team Review Underperforming Technical Team 153