Here is an extract (pages 106-113) I would like to share because it gives a brilliant overview about Lean, Scrum, XP (Extreme Programming) and Kanban.Continue reading Learn from the Trenches – Lean, Scrum, XP and Kanban in a nutshell
Introduction to Certified Scrum Master
Who is the Scrum Master?
In one of our previous blog posts, Rumesh Wijetunge wrote some relevant insights about the role of Scrum Master. Wearing different hats, coach, enabler, facilitator, team leader, problem-solver, s/he is in charge of giving right directions to team members so that they reach objectives. First promoter of Agile mindset, values and principles, the Scrum Master uses the Scrum framework to help a team understanding, working on and achieving a common goal.
I) Introduction to Professional Scrum Master
Who is Professional Scrum Master (PSM)?
We partially give some elements in a previous article on our blog: “ How To Choose A Scrum Master? “. On top of that, it is important to highlight that the Professional Scrum Master wear different hats according to the context: s/he is a coach, facilitator, enabler, problem- solver, proxy. His/Her main characteristic is to embody Servant Leadership. And basically, as the first promoter of Agile in the organization, s/he truly has the Agile mindset and is more than willing to share it.
The 5 correct answers are at the end of the post. Feel free to put a comment and tell me your opinion about this (easy) quiz.
I have been working in an Agile environment for some years, and I have always felt at my ease. Why? In a short, because the 12 Agile principles are ‘common sense’ to me, I feel well and easy to understand and apply them.
Let’s take them one by one.
When talking about Agile, Scrum and Kanban are among the most notorious frameworks. One used to hear: “I want to do Agile, let’s perform Scrum or Kanban”. Because they distinctly bring added-value to specific contexts, this is relevant to keep in mind their very own particularities.
Some days ago, a colleague told me:
– « Some people in my department run a daily meeting of one hour, sometimes even more. No agenda, barely some actions to be taken, only debating about ideas. »
– (Me): « Why do not they use Scrum approach and especially the Daily Stand-up meeting? »
– « This would be the same problem, daily meeting is not useful. This is better to do meeting when necessary. »
– « A short (and timeboxed) meeting is very useful », here is why…
The Daily Stand-up meeting (DS) must be done in 15 minutes maximum and involve maximum 9 people. It is a mandatory components of Scrum framework and is very enriching and useful for these reasons: