Project Management

Please login or join to subscribe to this thread

How would you motivate an Agile Scrum Team?

linkedin twitter facebook   Agile  
avatar
Jonathan Doyle PM Consultant| Adduco Consultancy Ltd London, United Kingdom
Hello, I've recently joined a company to run their projects using Agile.
During the daily stand-ups I've noticed members of the team giving updates one-by-one and not really engaging with each other. It also looks like the company board hasn’t been updated as when the product owner asks questions the team moves items with statements like “Oh yeah, I did that Friday”.
Looking in JIRA I can see that the team’s velocity goes up and down sprint-by-sprint and last sprint they only completed half of the items they accepted into the sprint. I've also noticed that the burndowns for previous sprints tend to be fairly flat until the last few days of the sprint when items start getting done.
The product owner has pulled me aside and explained that there’s an important milestone coming up and he doesn’t have confidence that the team will deliver all the work that he has planned.
Senior leaders have concerns regarding the product team, what is the best approach to lead the team towards success using Agile?
Sort By:
< 1 2 >
avatar
Jonathan Doyle PM Consultant| Adduco Consultancy Ltd London, United Kingdom
May 08, 2020 3:00 PM
Replying to Kiron Bondale
...
Jonathan -

With regards to ceremonies, it would help to know how those were originally introduced to the team. Do the team members (including the PO) fully understand the purpose behind them or are they just going through the motions (e.g. cargo cult)?

Are there any working agreements defined by the team? Have they come up with any simple documentation for their "way of working"?

Kiron
Hi Kiron, I agree. In fact I think that there may be some training issues here. I suspect that some members are new to the Scrum team and might have either picked up bad habits from other teams or have come from companies who weren't really using Scrum. The Product Owner seems quite knowledgeable about their role, perhaps not so well informed on what the Dev team should be doing.

Thanks, Jonathan
avatar
Jonathan Doyle PM Consultant| Adduco Consultancy Ltd London, United Kingdom
May 08, 2020 5:58 PM
Replying to Thomas Walenta
...
I would do a 1:1 with each team member and find out what inhibits this person to excel. Might be team problems, process problems or governance problems. Velocity just shows symptoms, not root causes. Same to insecurity on PO side.
Hi Thomas, that is a good point. I was thinking of catching up with a few of the team members before the retrospective. However, it has to be a balancing act as I want them to refrain from blaming each other for things as that could damage moral even more.
avatar
Jonathan Doyle PM Consultant| Adduco Consultancy Ltd London, United Kingdom
May 08, 2020 7:32 PM
Replying to Drew Craig
...
Hi Jonathon - We don't want to make the assumption of ill intent of any of the anti-patterns mentioned. I'd recommend taking time to understand where the team is hand how they got there, what their training and support have been like, and what their understanding of where they fit in is.
Many times, it is how the team(s) perceived the training. Without proper coaching, the team will do (and continue to do) what they feel is right or working.
Work with the team toward a reset. It will do no good to point out what you think they are doing wrong or what they could do better. Take time to understand their current state and provide them with the knowledge to develop different behaviors.
Growth and change happen through a slow course correct with buy-in, not by grabbing the wheel from the passenger seat mentality.
By all means, not saying that is what you are or plan on doing, just as a point of reference to solidify a point.
Hi Andrew, I concur with your points. I certainty see the approach that you have outlined as part of my phase 2. Phase 1 is just getting as many quick-wins in as possible to start helping the team improve. There then needs to be a closer look at the core challenges and try and address those. It certainly feels that phase 2 will be for a long period of time. Much training and support from me will be needed to get the guys back on-track. Moral is also key so I will have to tread carefully so that when I examine closely the root causes the team don't get caught up in a blame culture. That would be detrimental.
avatar
Adrian Carlogea Australia
I am surprised that all the answers here don't say anything about the actual technical challenges that may cause issue with the team. When I used to work as a software developer with Scrum all the issues that we got were related to the actual technical challenges and not to the Scrum framework or work behaviors.

Obviously I don't know what the issues are in this case but if they are technical in nature then I don't think any of the given advises would work. The issue may not be the fact that the team is not properly using Scrum or the team members are not "Agile" or they are not motivated.

I believe people overestimate Scrum, Agile and work methodologies in general. It is not Scrum, or whatever other methodology, that brings success to a work activity, but the hard skills of the people that are actually doing the work. Motivation does play an important role but a highly motivated team would fail if it lacks the required hard skills while a less motivated one made up of very good workers would succeed.
...
1 reply by Kiron Bondale
May 11, 2020 8:22 AM
Kiron Bondale
...
Adrian -

perhaps you missed the first line of my original response "I think you need to understand what is causing these challenges."

:-)

Kiron
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
May 11, 2020 6:40 AM
Replying to Adrian Carlogea
...
I am surprised that all the answers here don't say anything about the actual technical challenges that may cause issue with the team. When I used to work as a software developer with Scrum all the issues that we got were related to the actual technical challenges and not to the Scrum framework or work behaviors.

Obviously I don't know what the issues are in this case but if they are technical in nature then I don't think any of the given advises would work. The issue may not be the fact that the team is not properly using Scrum or the team members are not "Agile" or they are not motivated.

I believe people overestimate Scrum, Agile and work methodologies in general. It is not Scrum, or whatever other methodology, that brings success to a work activity, but the hard skills of the people that are actually doing the work. Motivation does play an important role but a highly motivated team would fail if it lacks the required hard skills while a less motivated one made up of very good workers would succeed.
Adrian -

perhaps you missed the first line of my original response "I think you need to understand what is causing these challenges."

:-)

Kiron
...
1 reply by Adrian Carlogea
May 12, 2020 5:11 AM
Adrian Carlogea
...
My apologies Kiron. :)

But I still have the impression that people put too much fate in Agile or in all sort of "frameworks" and have the impression that if you apply the methodology correctly and have people motivated then you would automatically be successful. I don't believe that.

I am not saying that the above does not help but I believe that the hard skills of the team members are more important for the success. If you are doing "Agile" right (whatever that means) you have no guarantee that you would be successful.

Motivating people and getting rid of bad work behaviors would definitely give you better changes for success but this is not enough. My experience with Scrum was that what was keeping us from achieving success always had to do with technical issues.
avatar
Adrian Carlogea Australia
May 11, 2020 8:22 AM
Replying to Kiron Bondale
...
Adrian -

perhaps you missed the first line of my original response "I think you need to understand what is causing these challenges."

:-)

Kiron
My apologies Kiron. :)

But I still have the impression that people put too much fate in Agile or in all sort of "frameworks" and have the impression that if you apply the methodology correctly and have people motivated then you would automatically be successful. I don't believe that.

I am not saying that the above does not help but I believe that the hard skills of the team members are more important for the success. If you are doing "Agile" right (whatever that means) you have no guarantee that you would be successful.

Motivating people and getting rid of bad work behaviors would definitely give you better changes for success but this is not enough. My experience with Scrum was that what was keeping us from achieving success always had to do with technical issues.
...
1 reply by Kiron Bondale
May 12, 2020 8:03 AM
Kiron Bondale
...
Adrian -

We are in total agreement here - agile is NEVER the silver bullet to slay all the dysfunctions of a delivery organization, whether those relate to management behavior, engineering practices or other sources.

The only thing which agile can do, if properly embraced, is to surface such issues faster than a traditional approach might.

Kiron
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
May 12, 2020 5:11 AM
Replying to Adrian Carlogea
...
My apologies Kiron. :)

But I still have the impression that people put too much fate in Agile or in all sort of "frameworks" and have the impression that if you apply the methodology correctly and have people motivated then you would automatically be successful. I don't believe that.

I am not saying that the above does not help but I believe that the hard skills of the team members are more important for the success. If you are doing "Agile" right (whatever that means) you have no guarantee that you would be successful.

Motivating people and getting rid of bad work behaviors would definitely give you better changes for success but this is not enough. My experience with Scrum was that what was keeping us from achieving success always had to do with technical issues.
Adrian -

We are in total agreement here - agile is NEVER the silver bullet to slay all the dysfunctions of a delivery organization, whether those relate to management behavior, engineering practices or other sources.

The only thing which agile can do, if properly embraced, is to surface such issues faster than a traditional approach might.

Kiron
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

ADVERTISEMENT

Sponsors