Certified Scrum Master (CSM) Certification in USA

1. Every team member is given stick-it notes and asked to write their views about the project, deadline, completion etc.
2. A good 3 minutes is given to each person to fill the following blank we can complete the task when we ……………………. Let each write their want. They can write 3 to 5 ideas.
3. Ask everyone to read one idea each and make sure that the other person does not repeat the same idea.
4. Have one person to make a note of all the ideas on the board.
5. Take voting from all to come to a common working agreement from the list mentioned in the board.

The objective of release planning is to plan and make the scope, budget, and date for the incremental delivery in an agile project. Planning to have multiple sprints until the final product is released is discussed in the release planning meeting.

Every member of the scrum team and the stakeholders are part of this release plan meeting and it happens during each sprint activity. The release planning is done with the help of the product planning output and the pace at which the team completes the product backlog item per each sprint. This pace is nothing but the speed of the team and termed as velocity in agile projects.

• Four or more week longer sprints
• Bigger team size
• Complex backlog items

• What it does – the functionality and the features
• How does it perform – Acceptance criteria

The course will educate all participants from the basics of agile software development. Hence it is important that one should understand agile as an empirical process against the waterfall approach which is a defined process.

You will be taught to Plan, Execute, Check and then Adapt. Yes, CSM course begins with the detailed introduction to the iterative four-step approach.

Yes, that’s how you can easily remember the five values of the scrum process. C FOR C means to Commit you to need Courage. To develop Courage you need to Focus With Open mind and Respect all in the team.

You got it right, it is Commitment – Focus – Openness – Respect – Courage

Develop these five values and every scrum team will see success. Commit to the Sprint Goal and focus to work towards the same. Share your views openly and respect others opinion as well. Have the courage to accept what went wrong in a retrospective meeting to complete backlogs in your next sprint.

The elevated view from above about scrum is called the aerial view of Scrum. It is a neatly-documented framework that will address the facilitating limitations we relate to the situation when there is any lack of details.

The project is split into sequences of iterations and completed phase by phase.

The framework of Scrum is simple and it deals efficiently with the changing situations. The work gets split into iterations. It is because during the development process the priority changes due to the situation, user mindset, technology etc. Therefore, the framework focus on splitting the project into sequences of iterations called sprint. Every sprint will last for maximum 4 weeks. Therefore the complexity of the project is split and all changes are accommodated during the sprint meeting. There is not much of loss and also the user gets the output per the expectation.

The framework is simply understood as Planning – Executing – Learning – Taking Actions. This will continue until the end result is achieved. Every sprint meeting will be in length to plan from the education of the previous sprint.

The evidence of human action is called arti ‘fact. In the scrum, it is represented in the form of a list, graph, etc. Artifacts are called information radiators. With this radiators, it is possible to achieve transparency in scrum projects which is one of the pillars of the empirical scrum process. Among the many, the three main artifacts are product backlog, sprint backlog, and increments.

Product backlog – The list of deliverables required from each individual is called the product backlog. The product owner will list the work and creates a backlog in each person name. The items are prioritised and one on the top needs immediate action.

Sprint backlog – The list of work taken for completion during a sprint meeting is called sprint backlog. During daily scrum, the team updates the sprint backlog to know where the team is still the next sprint meeting.

Increment – The completion of each product backlog item at the end of the sprint is called a product increment.

The three key stakeholders in the scrum team are the product owner, development team and the scrum master. These roles are looked upon based on their command and responsibility.

• Product Owner – The person who is responsible for prioritizing the work and one who owns the ROI of the project is called the product owner. This person understands the customer need and creates the product backlog.
• Development Team – The set of people who are involved in writing code and developing the project is called the development team. These people will be assigned product backlog and will focus on completing the same.
• ScrumMaster – The scrum process is implemented with the help of the scrum master. This individual bridges gap between the team and the product owner. He/she hears the team view to help them resolve issues to work towards the goal of the company.

Every product backlog item gets declared as DONE it must be accepted by all team members and they must in advance know when it is called DONE. Here the team must be appraised of how a work is done, what are the standards required to be obeyed, and the different ways to verify whether it is done.

Each user story will have a specific criteria description called the acceptance criteria for that story.

Every product backlog item gets declared as DONE it must be accepted by all team members and they must in advance know when it is called DONE. Here the team must be appraised of how a work is done, what are the standards required to be obeyed, and the different ways to verify whether it is done.

Each user story will have a specific criteria description called the acceptance criteria for that story.

Unlike in waterfall method, QA role is to write test cases and report bugs, in a scrum team QA has an extended role. QA team takes part in the daily meetings along with all team members. They are allowed to discuss with the business analyst and development team. They are part of the test planning phase. The team not only writes test cases but also the acceptance test cases to provide support to the product owner. Story estimation sessions will not happen without the QA team. They help in providing more realistic estimates. In short, the QA team is as equal to the development in the scrum projects.

Scrum process empowers the team to speak and share their views. Therefore scrum managers must understand the team strength and the product owner need. The manager should discuss with the team and let know the product owner to decide on the product backlog item. This will motivate the team to work towards delivery. The manager must never be biased and push team for delivery. Ensure that the team commits and support them during every sprint to combat issues. The manager must not think of bossing around but work along with the team to lead them to successful completion.

These days working with people across the globe on projects cannot be avoided. It is not possible to meet all at one table to discuss. Therefore managing teams with documentation might be effective but time-consuming and hence organization must embrace an agile way to work with distributed teams.

Even though it has its own flip side, still it is the best way to work with distributed teams. Remember that people remain the same irrespective of the geography and hence getting work done by setting expectation is quick. Also, use technology to meet people for daily stand up and execute the project efficiently.

• Tuckman’s Group Development Tools and Technique – Forming, Storming, Norming, Performing, Adjourning.
• Scrum Master tools Cynefin Framework – Simple, Complicated, Complex, and Chaotic.
• The Japanese Shu Ha Ri – Shu – self-disciplining, Ha – Innovate things, Ri – Execution
• Root cause analysis

1. Every team member is given stick-it notes and asked to write their views about the project, deadline, completion etc.
2. A good 3 minutes is given to each person to fill the following blank we can complete the task when we ……………………. Let each write their want. They can write 3 to 5 ideas.
3. Ask everyone to read one idea each and make sure that the other person does not repeat the same idea.
4. Have one person to make a note of all the ideas on the board.
5. Take voting from all to come to a common working agreement from the list mentioned in the board.

The people responsible for coding and developing the project is called the development team. The team that test the bug and fixes the issues is called the testing team. As far as scrum projects are considered the entire team is called a scrum team which includes developers, testers, product owners, scrum master, and the high-level stakeholders. These teams are self-organising in agile development and are independent to complete their task. They don’t require anyone to monitor but they manage themselves.

The objective of release planning is to plan and make the scope, budget, and date for the incremental delivery in an agile project. Planning to have multiple sprints until the final product is released is discussed in the release planning meeting.

Every member of the scrum team and the stakeholders are part of this release plan meeting and it happens during each sprint activity. The release planning is done with the help of the product planning output and the pace at which the team completes the product backlog item per each sprint. This pace is nothing but the speed of the team and termed as velocity in agile projects.

• Four or more week longer sprints
• Bigger team size
• Complex backlog items