• About

Brigitte Maenhout

~ Life is learning while adding value

Brigitte Maenhout

Tag Archives: self-development

The ‘so that’ of refinement.

05 Wednesday Nov 2014

Posted by Brigitte Maenhout in Agile Scrum

≈ Leave a comment

Tags

agile, brigitte maenhout, business process, business value, cognitive psychology, drive, economic success, empowerment, experiment, flow, happiness, highly efficient teams, scrum, scrum master, self-development

Agile is so effective because it has a lot of hidden tools in it that work. Surprisingly, a lot of the scrum masters and even Agile coaches that I have come across don’t talk about these things. Some don’t know about them, some choose not to reveal them, some even think it’s not part of their job to care….

But, I am a strong believer in clarity, as clarity creates meaning, meaning creates purpose and purpose is one of the corner stones of motivation, which ultimately leads to higher efficiency and thus, higher business value.

When people know the WHY, they will follow, they will learn, they will care. ( why do you think the most successful leaders focus on WHY and not HOW )

I am going to talk a little bit on how I do refinement. Not saying it’s the most effective way and you SHOULD be doing it like this, no, you have your team, you have your style, you will learn what works. But, I do want to show you what has been very successful for me and my teams.

REFINEMENT PHASE 1:

– I have 2 refinements, for a 2 week sprint, in the middle of each week. They are 2 hours long at the moment, because our team is not fully aligned yet. They will become less time consuming over time. But you look at your team and at your needs.

Take a look at this MVP drawing I did on the train this morning, this is the visual representation of my refinement ( phase 1 = week 1) – the second refinement is slightly different, but more on that later.

Agile refinement Phase 1

Agile refinement Phase 1

Phase 1:

Input ==> Prioritised backlog of cards

Iteration per card:

  1. Use a visual reminder of what we are trying to get to: estimation in T-shirt size. (WHY? Are the estimations that important? They are important for different reasons, but one of the hidden gems will become clear when you read on, it’s a tool to make sure the team is on the same page and to create more x-functional mindset)
  2. Ask the PO and the team for clarity on 2 subjects: Business requirement and the detail of what they need/want + How the team thinks of tackling this ( on a high level ) – PO should not interfere with the how, but in my team, he does have a voice and we can openly discuss things because it aids in cooperation and x-functional nature of the team, it brakes down tribes and creates a vibe of truly working together to create business value. BUT… in some teams, you CANNOT do it. If you have a PO with the tendency to micromanage, do not give them a voice until you have coached them into being more efficient.
  3. SM: Do we, as a team, have a clear enough understanding of what is involved to do a high level estimation? Yes? OK, 3,2,1 – estimate!!!
  4. If you notice a big diversity of estimation, it means one of 2 things: 1. your team is not estimating as a team (yes, I ask them to estimate as a team, because it has proven much more efficient – promotes x-functional, understanding of each others challenges, they become a more tight business unit and less risk of silo-ing) or 2. There is a level of un-clarity.
  5. SM: Person Small – Why? Person Large – Why? : You ask the extremes to make their cases, the team chips in when they do and the blanks get filled in, the misunderstandings surface and the team reaches a mutual agreement.
  6. Re-estimate.
  7. All on same level – great, we all know what to do on a high level, we have surfaced effort, complexity and our level of understanding to PO and we have done it as a team, ready to go for it and deliver that business value!!! 🙂

So the hidden gems:

  • Estimation as a team creates understanding and respect for each others challenges
  • It’s the basis of x-functional
  • It highlights where there is misunderstanding
  • It highlight areas of improvement in individuals and teams ( is someone constantly estimating too high? Why is that? lack of confidence? more experienced, so they know what is REALLY involved? Tendency to be to perfectionist and not lean enough – depends on case by case of course, sometimes perfection is needed…)
  • It creates a common purpose, the basis of mastery and… they did it all themselves ( autonomy – growth ,…) => basis of motivation ( autonomy, mastery, purpose)

I actually use bright coloured cards with cardboard 3D letters of S, M, L, XL and the physical cards. We have everything in JIRA too, but screens are banned during that meeting… all for a reason.

Why a tangible visual? Cognitive psychology has shown us an insight in how our brain works, the more we understand it, the more we should use that knowledge to find the most effective communication tools. The brain creates meaning through the senses. Visual is one of those senses. Our primary visual cortex picks up basic shapes initially ( circles or squares ) it relais info to the other areas in our brain: Ventral stream, Dorsal stream and limbic system. Respectively for the WHAT (its a card, its a letter), the location of the body in space and the feeling, gut, strong emotional reaction.

I use all of the above to add to the experience, and why not? science it there to use, not just to be interested in. Win-wins for the win 😉

And… it works. You actually see it during refinement, people are more involved, they stand, they sit, the move around, the physically move the cards… it helps embed all the info and associated info in the brain…

We’ve got the tools, we’ve got the knowledge,… use them, explore them, improve them 🙂

The paradoxes scrum masters face

22 Sunday Jun 2014

Posted by Brigitte Maenhout in Agile Scrum

≈ Leave a comment

Tags

agile, brigitte maenhout, business process, business value, empowerment, optimise, process analyst, scrum master, self-development

As a human being, you have different sides to your personality and sometimes,
those sides don’t always see eye to eye and you are faced with internal struggles, deciding what to do.

Nothing in life is ever black and white, and for a scrum master, that is no different.
A scrum master is faced with paradoxes, the role itself is a huge paradox, servant-leader (or at least, at first glance it seems to be so)
I feel that, managing those paradoxes shows how skilled you really are, more than that, it is part of the attraction of being a scrum master.

One of the paradoxes that I would like to take a closer look at is the Agile fundamental of ‘delivering business value’ and the ‘protector of the team’.

Business value is a very wide term, and does not just apply to the product you are delivering. You need to be sensitive to all elements at play.
What stakeholders are involved and what are their ‘other’ agenda’s?
I have encountered several companies where some stakeholders had as part of their agenda to see agile fail,
because it wasn’t the ‘right’ manager, team or project that was introducing Agile.

For me, part of being a scrum master is picking up on those things and seeing how you can be true to the agile values in the best way, always with the bigger picture in mind.
Is there a one size fits all solution? No there isn’t. I always try to find out why those agenda’s are there, what is the underlying need?
Can you find a different solution to meet that need and create a win-win? Sometimes the anwser to that is no, but at least it gives you information to find solutions.

Another challenge is the work load of a team, or even how self-empowered a team can be at what stage. Again, I believe there is no ‘one’ right solution, different scrum masters will have different approaches.
Some teams are very new and might need some guidance in the beginning, especially if you have external forces at place.

Let’s say you let them fly and they crash and burn, great lesson and they will be so much stronger for the next iteration, but combine that with an environment like I described above and there might not be a next time.

And what if your team has internal struggles themselves?
Not every one can cope yet with crash/burn/learn. Again, you need to be sensitive to these dynamics.

That’s what makes it fascinating, and the more you are faced with these challenges, the more you learn as a scrum master, the more value you can add and the more valuable you become.

What do you think?

Yours truly,

Brigitte.

 

 

 

Subscribe

  • Entries (RSS)
  • Comments (RSS)

Archives

  • December 2014
  • November 2014
  • September 2014
  • July 2014
  • June 2014

Categories

  • Agile Scrum
  • Highly efficient teams

Meta

  • Create account
  • Log in

Create a free website or blog at WordPress.com.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
  • Subscribe Subscribed
    • Brigitte Maenhout
    • Already have a WordPress.com account? Log in now.
    • Brigitte Maenhout
    • Subscribe Subscribed
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...