Agile Maturity Self-Assessment Survey (Published at ScrumAlliance)

Sharing my recent article publish by Scrum Alliance today, Tuesday 8th of December 2015.

This article identifies questions you can use to create an Agile Maturity Self-Assessment Survey, and it discusses the importance of this type of survey.

You might be asking why you would need a survey. Well, I truly believe in constant feedback. There is no better way to challenge the status quo. Also, it helps us understand what we can improve, how to be faster, and how to be more adaptive and responsive to the changes or challenges that come our team’s and business’s way.

Keep in mind that these kinds of tools are what allow us to improve what we already do well and to help us gain a clear view of where we need to focus our efforts. To that end, I think that the best place to retrieve this feedback is from the people who deal with the real scenarios every day. They are the best at evaluating their team and business for Agile maturity so that they can identify the anti-patterns and develop possible solutions and corresponding actions for improvement.

For these reasons, some time ago I searched on the Web for existing surveys that I could use and was able to find one that, from my perspective, was complete and had all the right questions.

So, the next step was to create the survey and send it to everyone. The number of replies was very good, and some conclusions were interesting, but (there is always a but) the survey feedback included the following remarks:

  • It was too long.
  • Some questions were not clear enough to understand and answer.
  • Some of the questions were hard to answer because they didn’t have a full overview.
  • It was confusing if you did not have a Scrum role.

Again, after this feedback and based on my beliefs, I decided to collaborate with a few people who answered the survey and a few others who face these challenges every day. These collaborators have also decided to accept the challenge to become Agile Champions or Change Agents.

I was amazed by their motivation and commitment to help improve the survey and their commitment to understand its results. It was really impressive!

After long discussions and reviews, the result of this collaboration was the following improved survey:

Your Role

  • Dev Team Member
  • ScrumMaster (dedicated)
  • Product owner / Manager
  • Delivery Manager / Head of / Director
  • Project / Program Manager
  • Other

1. Which Agile framework does your team use?

  • Scrum
  • Kanban
  • Other
  • None

2. Is your team able to deliver valuable software frequently?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

3. How often do you think that we are delivering what the business needs most?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

4. Is your team accommodating all the changes suggested by the product owner?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

5. How often does your team have visibility into what it will be doing in the next three sprints?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

6. Does your team have an agreed and clear DoR (Definition of Ready)?

  • Yes
  • No

7. How often are the user stories that enter your sprint ready to be implemented?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

8. How often is your team being disrupted and controlled by outsiders during the sprint?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

9. Does your team find blockers during the sprint?

  • Yes
  • No

10. Are any blockers found being tackled in a timely manner?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

11. Is your team collaborating daily? (Ex: Daily stand-up)

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

12. Is your team motivated to deliver the sprint deliverables?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

13. Do the Scrum team members trust each other?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

14. How often, when it’s possible, does your team communicate face to face?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

15. Does your team have an agreed and clear DoD (Definition of Done)?

  • Yes
  • No

16. How often is your team able to deliver fully tested, working software at the end of the sprint?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

17. How often is your team able to deliver at a sustainable pace?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

18. Is your team striving for quality and technical excellence by Betfair standards?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

19. Is your team self-organized in accordance with Agile principles?

  • Yes
  • No

20. Are the team members locked into their specific roles?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

21. How often is your team able to reflect on whatever has happened? (Ex: Retrospective)

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

22. Does your team take appropriate actions based on whatever has come up in retrospectives?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

23. Is your team continuously improving what it does (including processes)?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

24. Is your team using performance metrics to improve team performance?

  • Never
  • Seldom
  • Sometimes
  • Often
  • Always

25. Do you have any ideas on what we could improve regarding our software development process?

  • (Open Question)

My thoughts are to continue to analyze the next feedback and review this survey periodically with all the Agile champions (each time with a small group to be able to stay focused).

Please let me know if you have any questions or if you want to share your own experience on this subject. I would like to hear your thoughts and opinions.

See more at: ScrumAlliance.org | Agile Maturity Self-Assessment Survey

When to take the decision? What decision? by Nick Maroudas

Today, I would like to share with you an article written by my friend Nick Maroudas.

After reading his article “When to take the decision? What decision?” I thought that was really great to share with you.

So, my next step was ask him if I could share the article in the blog and after a few seconds I got his answer as you can see “Accepted you can take it 😄”.

Having said this, I’m happy to share the article link:

When to take the decision? What decision? by Nick Maroudas.

Nick

My feedback from this is simple: Great article. I hope that you enjoy reading it like I did.

Lean Coffee Portugal Community!

After the Lean Coffee Porto and Braga continued success, today’s post is related with the most recent update that is Lean Coffee Portugal.

Logo Portugal

It’s really amazing to see this community growing month after month. Better than this, is the people’s motivation attending every month as well the new people joining our community.

The result from this is the 9th Edition in November @Startup Braga and the expectation to keep coming and growing!

I will be there and you? Are you joining us to share your knowledge and experience?

CAS 2015 Agile Spain :: TALK Why for Some Product Owners and Stakeholders Agile is Like Crossing Over to the Twilight Zone

Was with great pleasure that I found out last week 20th of Oct 2015 that:

“Yesterday we finished the selection of talks and workshops for the conference, and your proposal was selected. I’m talking about “Why for Some Product Owners and Stakeholders Agile is Like Crossing Over to the Twilight Zone”.

Congratulations!”

I’m really happy to be one of the speakers for this conference. Nevertheless, share and learn with everyone!

See you there 😉

Road Maps and Release Planning – The never-ending story (Published at ScrumAlliance)

Sharing my recent article publish by Scrum Alliance  on 6th of August 2015.

Again its a very interesting and hot topic called “Road Maps and Release Planning – The never-ending story“.

I hope that you like reading this article as much as I enjoyed writing.

Why for Some Product Owners and Stakeholders Agile Is Like Crossing Over to the Twilight Zone (Published at ScrumAlliance)

I’m happy to share with you that I have my first article approved and publish by Scrum Alliance  on 23rd of July 2015.

Its a very interesting topic called “Why for Some Product Owners and Stakeholders Agile Is Like Crossing Over to the Twilight Zone“.

I hope that you like reading this article like I enjoyed writing it.

Agile Champions the new Change Agents!

As promised in my previous post “Does the Change Agent Networks work? In my case the Agile Champions…” I said that I would share some conclusions about this model implementation.

During this time I didn’t said nothing because I needed some time to start seeing the first results. Well, good or bad…

As you know, transforming mentalities doesn’t work from night to day. In reality takes time and in some situations more time than expected.

Having this said, I would like to start by giving some context in case that you are reading this Blog/Post for the first time.

As an Agile Coach I’m responsible for providing guidance and support in agile concepts and principles to multiple teams distributed across 3 locations (Portugal, United Kingdom, and Romania) in the company that I’m currently working.

After working for a period of time with different environments and cultures, I’ve realised that some times it’s really hard to help people to change even when that change is beneficial to them, others and the business.

So, during one of the many conversations that I had, one person in particular asked why shouldn’t we try to motivate and empower people to be change agents? From that moment I started to plant this idea, like a seed, in everyone’s mind.

Now it’s the time to share some conclusions but please keep in mind that this is work in progress. In other words this is on-going work will never be complete.

The first step was do a roadshow by all locations with the objective to share what was an Agile Champions and what was expected from them. The first reaction was not what I was expecting. Meaning that, almost everyone was with the suspicious look. Also, because cause some confusion. They thought that was another role or more responsibilities added to their current role if they accepted.
From this moment, I had to keep working with them. Clarifying any existing doubt what was an Agile Champion “ An Agile Champions is some one that truly believes in Agile and the change. Believes what are the benefits that can come with the change and is ready to take actions to bring more people on board”. I can say that was a motivational and coaching continuous work.

After achieving this first step, some people started to attend the weekly meetings. During this meetings we discussed what could motivate people to become an Agile Champion, to attend the Agile Communities sessions (share and learn) and to have the will to take actions and bring more people on board. Agin, this was another critical moment. Lucky went well since I had people believing in Agile and committed to this, as well, the Leadership Team support. They were the key to keep this proceed to success even in a slow pace.

It’s funny because if I go back in time, the reality was that I only had one or two Agile Champions since the beginning. Was our work together that made more people to believe and have the will to join us.

At this moment in time we had a small group on each location but I still had the need to drive these meeting and communities. Everyone was expecting that even during this time I was saying that would be really great if they wanted to do it.

Luckily or not something happen accidentally. After a few months suddenly I had the need to start traveling more. Meaning that, I was unable to attend all the weekly meetings and community sessions on all locations. The surprise was that in a natural way they were more committed and self-organised than they and me were expecting.
They started to schedule the weekly meetings, discuss what they could do to keep improving, talk about ideas for the Agile Communities on each location, how to involve and bring more people on board.

For me this was a magical moment! The moment that the Agile Champions had become Change Agents! The moment that I truly believed that the viral change was going to work!

Please let me know if you have any question or share your own experience on this subject. I would like to ear your thoughts and opinions too.

Lean Coffee Braga Community!

After the Lean Coffee Porto continued success, today’s post is related with the Lean Coffee Braga.

logo-color-braga

This happened yesterday in the beautiful city of Braga at Primavera Software.

If you asked me some time ago “Did you believed that in a short period of time would exist the Lean Coffee Porto and 3 months later the Lean Coffee Braga would start”, I would say no. But I was wrong!

They are real, they are a big success!

Not just due to the Co-Founders but to everyone involved. That, after a day working day, they are still motivated to attend, share experiences and learn.

I’m a truly believer that together we can grow more and faster.

For more details please check the bellow links:

Many thanks to everyone for making this real!

Does the Change Agent Networks work? In my case the Agile Champions…

Well… I just started to implement this model in the company that I’m currently working and my first feedback is positive. But only time will tell if it was a success or not 😉

Lets go back in time to understand why we are trying this model.

As you know we live in a world that is made of different people, mentalities and cultures. Due to this, we need to keep improving and find new approaches and models to help implement changes.

After working for a period of time with different environments and cultures, I’ve realised that some times it’s really hard to help people to change even when that change is beneficial to them, others and the business.

Some time has passed, conversations and discussions took place with different people, but, one person in particular asked why shouldn’t we try to motivate and empower people to be change agents?

Why not try this approach?

From that moment I started to plant this idea, like a seed, in everyone’s mind. So far so good!

Coincidently, this week I was reading a book that elaborated on this same idea and I’ve summarised their thoughts on the following quote:

“You will need executives, managers and staff to act as change agents. That’s because people are more likely to listen to, and work with, their peers rather than external consultants or dedicated change agents.

People tend to feel threatened or feel that change is being pushed on them if they don’t see their peers jumping in first. This approach helps the change go viral, and helps build the momentum.

Here are some tips for expanding our change agent team:

  • Get at least one person from each business area that is affected by the change.
  • Set strong expectations with the early adopters that being part of the change team is extra work.
  • Make becoming a member of the change agent network exclusive in order to attract the right people. I’ve always wanted to try some American Idol style audition, but that has been to crazy of an idea for the organisations I’ve worked in!
  • Agree on rotating the type of change you’re implementing.

Most of all, give early adopters support, training, and some autonomy. Notice I said some autonomy. At this point you want the people who are motivated to help execute the change, but be aware, thy may not have the necessary skills you, as a change agent, have.

Change goes viral when people start helping other people adjust.

These people, who weren’t part of the core change team, starting taking ownership of roadblocks all the teams were facing. They would provide updates to the whole departement during our monthly retrospectivs and the change team supported their efforts.” [1]

As a last thought I will be sharing with you (when possible) all the experiences, situations, issues, successes about this path that I’m taking so we all can learn together.

References:

[1] Jason Little | Lean Change Management

Is trusting relationship and symbiosis a myth in Self-Organising teams?

As you know one of the Scrum Principles is Self-Organising Teams. This means that, the teams should include all required roles to bring the product or feature to life.  Also, all team members from the Scum Team must form a close and trusting relationship, a symbiosis in order to allow them to work together as peers. Shouldn’t exist us and them but only us.

Ir order to create this relationship and symbiosis they need pass through the four-stage model as described by Bruce Tuckman’s: [1]

  • Forming – Stage 1

In this stage, most team members are positive and polite. Some are anxious, as they haven’t fully understood what work the team will do. Others are simply excited about the task ahead.

As leader, you play a dominant role at this stage, because team members’ roles and responsibilities aren’t clear.

This stage can last for some time, as people start to work together, and as they make an effort to get to know their new colleagues.

  • Storming – Stage 2

Next, the team moves into the storming phase, where people start to push against the boundaries established in the forming stage. This is the stage where many teams fail.

Storming often starts where there is a conflict between team members’ natural working styles. People may work in different ways for all sorts of reasons, but if differing working styles cause unforeseen problems, they may become frustrated.

Storming can also happen in other situations. For example, team members may challenge your authority, or jockey for position as their roles are clarified. Or, if you haven’t defined clearly how the team will work, people may feel overwhelmed by their workload, or they could be uncomfortable with the approach you’re using.

Some may question the worth of the team’s goal, and they may resist taking on tasks.

Team members who stick with the task at hand may experience stress, particularly as they don’t have the support of established processes, or strong relationships with their colleagues.

  • Norming – Stage 3

Gradually, the team moves into the norming stage. This is when people start to resolve their differences, appreciate colleagues’ strengths, and respect your authority as a leader.

Now that your team members know one-another better, they may socialize together, and they are able to ask each other for help and provide constructive feedback. People develop a stronger commitment to the team goal, and you start to see good progress towards it.

There is often a prolonged overlap between storming and norming, because, as new tasks come up, the team may lapse back into behaviour from the storming stage.

  • Performing – Stage 4

The team reaches the performing stage when hard work leads, without friction, to the achievement of the team’s goal. The structures and processes that you have set up support this well.

As leader, you can delegate much of your work, and you can concentrate on developing team members.

It feels easy to be part of the team at this stage, and people who join or leave won’t disrupt performance.

This is why we should minimize any teams change since Its takes time to become a true team – a tightly unit with members who trust and support each other and who work together effectively.

Changing teams compositions makes the team-building process (four-stage model) all over again and in the end self-organisation suffer.

References:

[1] Mind Tools Club | Forming, Storming, Norming, and Performing, Understanding the Stages of Team Formation

[2] Businessballs | Tuckman Forming, Storming, Norming, Performing model