What You Should Know About Psm Exam

By Author: Subra Siddrehamian.
Total Articles: 6
Comment this article

If you are new to scrum, it is a methodology used to come up with software faster and efficiently in the developer’s stage. Since now that is cleared-up, a scrum master is the project manager of a developer team. As a scrum master one may have sat for the CSM or PSM exam, as there are two Scrum Master Certification tests available.

If you are new to scrum, it is a methodology used to come up with software faster and efficiently in the developer’s stage. Since now that is cleared-up, a scrum master is the project manager of a developer team. As a scrum master one may have sat for the CSM or PSM exam, as there are two Scrum Master Certification tests available. As the project manager in charge of a developer team, there are ways of carrying yourself to the benefit of the developer team and most to yourself. A software engineering team is a highly skilled grouping, and as such needs to be respected and treated as such. With scrum you and your team are supposed to be smooth-sailing from the get go, as everyone knows their role. When it comes to knowing their roles some project manager’s simply do not understand ...
... where they fit in. Here is some of the practices to avoid gaining notoriety with your developer team:

Be decisive: This means if you have picked items for either the product backlog or sprint backlog, do not acquire the habit of changing your mind. Changing your mind did not help you pass your PSM exam which helped you achieve your Scrum Master Certification, why start now? Changing your mind disrupts the flow of work done, if you have picked items for either the product backlog or sprint backlog, do not acquire the habit of changing your mind. Time is lost and you come out quite disorganized. Changing your mind disrupts the flow of work done by the developer team and leads to poor productivity.

Do not micro-manage: No-one appreciates working under pressure and mostly a software developer. Give them the breathing space they require, and ensure that they have what they need at all times to do a good job. If you are always checking after every 30 minutes how much work they have done, it is time to stop.

Do not assume: Be sure to keep up with the impediments your developer team may be facing. Many scrum masters assume that their developer team can handle everything. This does not give you a lee-way to micro-manage, it only means be a breadth with what your developer team is up to. Make sure during the daily scrums you note down the impediments being faced by your developer team, and see how you can advise and consul as necessary.

Make sure less time is spent on meetings: Meetings can be productive, but when all we do is talk, that is definitely a recipe for disaster. A daily scrum should take 15 minutes, where everyone knows where they are on the project.

Note that not the whole developer team has sat down for a PSM exam: Remember, that your whole team may not have a Scrum Master Certification, and as such it will be your job to bring them up to breadth with what is expected of them. Be sure to answer any of their scrum questions which they may bring up.

If you take this to heart, then probably you will develop a cordial relation with your developer team. Having sat for the Scrum Master exam do not let it go to waste because of a few bad practices. This article is not about how to be a Mr. nice guy, it is about how you can accomplish your projects faster. Time is money, and most of the steps mentioned, save a lot of time and confrontations.
Resource: http://www.castlebergoutdoors.co.uk/acatalog/Haglofs.html