Posted By SUDHA CHAITANYA on 15 Jul 2014 12:43 AM
I have attempted PSM1 three (3) times so far. got 68%, 77%, 77% so far. very dis-heartened and dis appointed. I read scrum guide, took several Open assesments (always got 100%), ...................anyone please advise what am I missing and how can I bridge the gap ?
Score breakown on 3rd attempt:-
Scrum Framework - 90%
Theory & Principles - 75 %
Cross-Functional, Self Organizing - 58%
Coaching & Facilitation - 57%
please let me know what books or materials should I read and whatever it takes me to complete the Test with Success, please advice.......
Do you work in an Agile environment ? Are you trying to relate the questions to what you do rather than what you should do ?
Have you read the discussions in the forum ?
Self Organizing teams was something which I had to learn on my PSM II for both attempts and the feedback I received was
"A Scrum Master's role is that of a coach and a teacher. Their primary responsibility is to teach Scrum's theory, practices and rules. If the question asks how would you respond as a Scrum Master, don’t only focus on what you would do to solve the problem, but instead include in your answer that your primary function is guiding the team to solve their own problems by using the three pillars of empiricism. It’s too easy to fall back on our natural inclination to use our wisdom to solve other’s problems, but that does not encourage self-organization. A Scrum Master is not serving a team when they do something that the team could do themselves. This does not encourage self-organization."
"The only place where you lost any fairly sizable number of points was in your description of what parts of Scrum help with self organization. Scrum, being a framework, doesn't mandate a number of the practices you included in your answer."
I found it easier (having not a lot of scrum experience) trying to relate Scrum to what we've done in the past... eg our projects that we used to laugh about and design on the back of our Cigarette boxes.
Initial goal for project, broken down into what were main objectives and parts, decompose one object and do that. Every morning look at what we had done, and think of what we were doing next (plan for the day approach), see any problems and come up with plan of what we were going to do. At the end of that section, when it was complete, integrate that and pick a new piece of work and start again. The downside of our technique, used to be if we had a complicated project, we need a bigger cigarette box, so we used to draw it on the whiteboard.
But being serious, are you concentrating on the scrum exam too much and being too formal, rather than thinking about what you have to do to get a product out and then reading the scrum guide and tying it in to what you need to get done.
It's like at work at the minute, we have an approach of developers doing what they want... they code and to hell with everything else. They took agile and bent it into something else, anything which doesn't involve code is a no no to them.
They each write their own code and then dump it on QA team, so when it falls over, it's because it wasn't tested (not their problem). Quality is none existent and the QA team is snowed under. Back to basics, when does testing begin and who is responsible for quality.
They do a token standup every morning, when the developers have no idea of what the goal of the sprint is or what each other are working on. They have managed to silo themselves not only into a team of only developers, but ones which don't understand each others work. The standup to them is not checking the plan and adjusting as necessary, its an opportunity to answer 3 questions with no meaning to them.
Now given that scenario, read the guide, apply the framework and you can see straight away how it would work.
Add a good dose of XP, pair programming, test driven development, story boarding etc,
From there, the exam will probably make far more sense