Skip to main content

CSM Exam - about time!

Reading Danube's blog The CSM Exam.

Some background - the CSM (Certified Scrum Master) is a certification by the Scrum Alliance that has been given to every (99.999% perhaps I exaggerate) one that attended the 2 day training program. The certification has been a contronversy for as long as it has been offered (many years now). The Alliance is putting a real written exam into place as a requirement for certification.

I think a real test is a GREAT thing. Given that it is a “certification”.

Definition of certification: a document attesting a level of achievement in a course of study or training.


Attendance, the previous requirement does not “attest to a level of achievement”.

In Danube's post they state:
“Of course, the flipside is that an exam will only test attendees on certain aspects of the Scrum framework in a format that does not necessarily promote a deep understanding of Scrum’s values.”


The assumption in this statement appears to be that the test is not well designed or that it cannot test values. I have not seen the test, but assume that it will test the knowledge of the values of Scrum. This is very testable. The certification (as typically applied in many industries) attest to the knowledge of a body of knowledge (BOK) (don’t go all PIMBOK on me - yes Scrum has its own BOK). The certification does not state that the bear has the attitudes and exhibits the behaviors of the values. Which I think is what Danube is concerned with in their statement about Scrum’s values.

So how does one test or assert the affective nature or the behavior nature of a person? This is typically done via case study of the person. Is this not what the next level of Scrum certification attempts to do? The CSP (Certified Scrum Practitioner) is a certification that attest that the bear of said certification (oh so formal - just say - the CSP) has shown (through self report) the values and behaviors taught in the BOK of Scrum.

Testing for CSM brings the Scrum certification into minimum compliance with the common understanding of the terms. That is a value of Scrum/Agile - to state clearly what we are going to do, then do it, and have an objective measure of DONE, demonstrate that level of DONENESS, and then be capable of continuing down the path.

I say - about time - what took you so long - and don’t give me that stinking incremental-iterative argument. The facts will not bear out the delay in a real test over how many thousands of CSM there are (982 pages A-Z).
Post a Comment

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

What belongs on the Task Board?

I wonder about these questions a lot - what types of task belong on the task board?  Does every task have to belong to a Story?  Are some tasks just too small?  Are some tasks too obvious?  Obviously some task are too larger, but when should it be decomposed?  How will we know a task is too large?

I answer these questions with a question.  What about a task board motivates us to get work done?  The answer is: T.A.S.K.S. to DONE!



Inherent in the acronym TASKS is the point of all tasks, to get to done.  That is the measure of if the task is the right size.  Does it motivate us to get the work done?  (see notes on Dan Pink's book: Drive - The surprising Truth about what motivates us) If we are forgetting to do some class of task then putting it on the board will help us remember.  If we think some small task is being done by someone else, then putting it on the board will validate that someone else is actually doing it.  If a task is obvious, then putting it on the board will take vi…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.