Scrum.org

JULY 29, 2019

In my role as an Agile coach and Scrum trainer, I get the chance to talk to a lot of Scrum Masters and teams. When I ask them about what their team is measuring, the most common answers I hear are velocity, story points, and burn-down charts. Makes sense, many Scrum Masters learn about those topics in an introductory Scrum course.

Technical Review 146

Technical Review Underperforming Technical Team Development Team Review Software Review 146

Scrum.org

JULY 1, 2019

Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.”. By consequence, teams will ultimately abandon Scrum in such environments. . Ask yourself how successful your Scrum in reaching those two objectives.

SCRUM 127

SCRUM Underperforming Technical Team Development Team Review Controlling 127

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 229

SCRUM Underperforming Technical Team Technical Review Software Review 229

The IIL Blog

SEPTEMBER 6, 2023

The History of Agile Project Management Agile project management emerged in the software development industry in the late 1990s and early 2000s. In 1991 the book Rapid Application Development was published and an approach of the same name, RAD, was born. Agile projects are iterative and have regular feedback loops.

Agile 88

Agile Underperforming Technical Team Software Review Development Team Review 88

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 Energy 193

Agilemania

FEBRUARY 21, 2023

Not maintaining requirements in an Agile team can lead to several challenges, including scope creep, missed deadlines, low-quality deliverables, and dissatisfied stakeholders. This can cause frustration for both the team and the stakeholders, as the project may require additional work to fix these issues.

Underperforming Technical Team 98

Underperforming Technical Team Agile Development Team Review Technical Review 98

MPUG

MAY 6, 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. Kyle: Hello, and welcome to part one of MPUGs Project Performance Measurement course. What does the team care about? You can’t influence that project.

Performance Measurement 52

Performance Measurement Underperforming Technical Team Software Review Governance 52

Wrike

JULY 6, 2022

Ultimately, it needs to prioritize and enable project work that IT teams can execute to align with your business initiatives. Over the course of a three-blog series, we want to take the next step into the IT PMO. Enabling transparency in IT operations and product development . Good IT teams can simply adapt to the challenge.

2022 41

2022 Underperforming Technical Team Development Team Review Technical Review 41

nTask

AUGUST 22, 2019

The term Agile refers to a way of managing projects that incorporates constant improvement, scope flexibility, team involvement, and delivering crucial quality products. This method often results in low-quality products due to delays in milestones, financial issues and lack of prioritized characteristics for the products.

SCRUM 132

SCRUM Technical Review Development Team Review Software Review 132

Scrum.org

OCTOBER 10, 2018

Indeed, the range from a Monte Carlo forecast can be more accurate and useful to a team in Sprint Planning than an absolute value, such as an average velocity or burn rate projection. In our earlier example, we knew the team velocities for seven Sprints, which were 114, 143, 116, 109, 127, 153, and 120 points. So, what can a 54.3%

Underperforming Technical Team 133

Underperforming Technical Team Technical Review Development Team Review Estimate 133

MPUG

DECEMBER 10, 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. Melanie: Okay, Melanie here with Team MPUG. There may be exclusions, such as those steps included in product demonstrations. Tim Runcie: I got a good group here today.

Software Review 52

Software Review Technical Review Underperforming Technical Team Engineering 52

Scrum.org

JANUARY 14, 2021

The Nexus group of teams is very similar to the Agile Release Train (ART) construct. In both SAFe/Scrum it is a self-managing team of self-managed teams with a couple of key roles at the team of teams level. . Lean/Agile Leadership. Nexus Integration Team (NIT) - System Team. Nexus - ART.

Cadence 139

Cadence Technical Review Development Team Review Lean 139

Leading Agile

JANUARY 28, 2019

I’m not suggesting this degree of simplification is automatically or always a Bad Thing. It can become a Bad Thing when we lose sight of the larger context of our work. Software developers/maintainers. It’s a Bad Thing to take that line of thinking so far that we forget about other stakeholders.

Agile 107

Agile Underperforming Technical Team Development Team Review Engineering 107

Leading Agile

OCTOBER 1, 2018

Mike Cohn’s August 2016 article, The Dangers of a Definition of Ready describes certain problems that can occur when a team uses the concept of a Definition of Ready. Below I review the LeadingAgile Compass model to try and provide context around Definition of Ready. A team is either “agile” or “not agile.”

Software Review 104

Software Review Underperforming Technical Team Technical Review Infrastructure 104

Leading Agile

OCTOBER 10, 2018

Most systems implemented in large IT organizations are point solutions implemented to solve local (departmental, business unit, or team) problems. I was showing their development teams how to automate functional tests using Cucumber. But if you tried to use one as a crop-duster, you’d achieve very poor results.

Technical Review 95

Technical Review Software Review Underperforming Technical Team Engineering 95

MPUG

DECEMBER 15, 2019

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. Tad: So these are things that we’ll be talking about today as we think about what we can do as individuals, as project managers, or participants in the broader team.

Innovation 40

Innovation PMO Underperforming Technical Team Technical Review 40

Herding Cats

FEBRUARY 9, 2019

There's been a rash of conjectures about all kinds of bad business, project, and software development (agile and traditional) management ideas of late. This also meant developing software systems to support this effort. We develop these reference classes using Agile Function Points. We use Vitech's Core.

Estimate 42

Estimate Technical Review Underperforming Technical Team Software Review 42

Teamweek

FEBRUARY 9, 2023

And, not surprisingly, the design process usually involves a whole team , rather than a single designer. Along with working with CEOs (mostly if you’re dealing with a startup), they also work closely with product managers, developers, QA and marketing , for instance. They’re key in the Prototype phase of the design process.

Development Team Review 52

Development Team Review Underperforming Technical Team Closing Controlling 52

Scrum.org

MARCH 19, 2023

This allows me to have a more up-to-date understanding of the world, including newer events and developments. 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.

ChatGPT 152

ChatGPT SCRUM Technical Review 2020 152