Leading Agile

APRIL 20, 2023

Empowering your teams isn’t about allowing them to make decisions in a vacuum and giving them free rein to do whatever they want. The days of providing a little guidance here, some methodology there, and letting the teams self-organize their way to success are behind us. What does it mean to empower teams?

Agile 62

Agile Underperforming Technical Team Cadence SCRUM 62

Planio

MARCH 13, 2023

The top 3 format Free project status report template 11 steps to write a project status report your team will actually read 1. Build your report where your team works 2. Don’t be afraid of bad news 10. Primarily, your project loses visibility and coordination with team members and key stakeholders unsure of what’s happening.

Underperforming Technical Team 78

Underperforming Technical Team Software Review Technical Review Risk Management 78

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. ' In deciding which feature to develop first, those with the highest economic value are selected. I do not think the teams have been weak at threat avoidance. What is a Risk-Adjusted Backlog?

Risk 145

Risk Underperforming Technical Team 2006 2012 145

Project Management Essentials

AUGUST 3, 2019

Experienced agile coaches and practitioners develop a sixth-sense. They can quickly assess the health of an agile project or team just as doctors do with their patients. In 2013, Mike Cohn coined the term scrum smells to describe the signs that a scrum team is in trouble. What are the team dynamics? Outsourced Agile.

Underperforming Technical Team 40

Underperforming Technical Team Agile Technical Review Software Review 40

Scrum.org

APRIL 21, 2020

We also see in the evolution of the Scrum guide how the distinctiveness has improved over time, for instance by dropping the term “team” in favor of “Scrum team” and “Development team”. Another example is how the Scrum guide separates activities from events: Events have a clear time-box, cadence, subject and participants.

Underperforming Technical Team 159

Underperforming Technical Team SCRUM Cadence 2019 159

Leading Agile

MARCH 23, 2022

More often than not in kind of either the IT product development space or IT services space. We like to consider ourselves kind of a full stack consultancy in the sense that you know, obviously, you have to deal with the work surface levels and what the teams are doing but you know, how do you orchestrate teams across dependency boundaries?

Agile 140

Agile Consulting Influencer Underperforming Technical Team 140

Planio

APRIL 24, 2023

Updating project management software to keep their team on track 9. In everyday terms, a project manager’s job is to oversee, coordinate, and lead their team from project kickoff to handoff. During project planning, the team gets into the details of their solution, understanding exactly how they will deliver on their promises.

Development Team Review 78

Development Team Review 2030 Underperforming Technical Team Risk Management 78

Resource Guru

OCTOBER 18, 2023

The result tells you the percentage of time that your team spends on projects that actually bring in money. A high utilization rate means your team is focused and efficient. Billable hours: These are the hours your team spends on client projects. Billable hours directly contribute to revenue.

Underperforming Technical Team 52

Underperforming Technical Team Software Review Technical Review Monitoring 52

Planio

MARCH 20, 2020

What’s the number one factor that influences whether your project is a success or a dud? Maybe you think it’s too much work for the size of your team. Or that your team already knows how to communicate. Not only that but finding the right cadence of communication can feel like a Goldilocks situation. Here’s an example.

Planning 122

Planning Underperforming Technical Team Defining Cadence 122

Leading Agile

JUNE 29, 2023

In fact, at conferences, we often talk about how managers are bad and executives are foolish people who want to derail the company. Just trust the teams. How about we let the teams decide how to work? Let me ask, are you all familiar with the ladder of influence? Do you think we should consider that perspective?

Agile 75

Agile Technical Review Executing Influencer 75

Herding Cats

AUGUST 5, 2017

For risks that are beyond the vision of the project team a properly implemented risk management process can also rapidly quantify the risks impact and provide sound plans for mitigating its effect. Hoping that the project will proceed as planned is naïve at best and poor management at worse. Hope is Not a Strategy.

Risk Management 42

Risk Management Risk Estimate Underperforming Technical Team 42

Herding Cats

APRIL 16, 2019

Product Development (#ProdDev). Agile Software Development (#ASD). The following material comes from conferences, workshop, materials developed for clients. Chartering the Team , Chartering empowers team members, both individuals and collectively. Cost, Schedule, and Technical Performance Management (#CSTPM).

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Leading Agile

MARCH 17, 2021

And I was working for this VP that was like really super cool, is very into agile and we were coming up with really creative things for like team formation strategies and agile governance, all stuff. And then the process developed a point of view around kind of why companies were jacking it up. What do you organize those teams around?

2021 62

2021 Agile Underperforming Technical Team SCRUM 62

PM That Works

MAY 9, 2020

I had a chance to join a mastermind with several of the john Maxwell team members. And so it's just a great community of people that are really driven to watch you grow in and master your influence to be able to really do the job that we were intended to do. I'd you know that my team needs that I'm you don't have to talk to me.

Agile 40

Agile Consulting Certification Executing 40

Leading Agile

MARCH 31, 2020

You get super clear backlogs, you find out what the real cadences you’ve finished work that you start. And I was working at version one at the time and so like I’m like all in like, not like team level scrum. And that was about the time that I was starting to develop the teams backlogs, working testing software.

Agile 71

Agile Technical Review SCRUM Engineering 71