SCRUMstudy Scrumvideo on the importance of creating project vision in Scrum

How to Identify Scrum Master and Stakeholder(s) in a Scrum Project?
In the Initiate phase, the first process is to create the project vision. After that, the next process is to identify the Scrum Master and the Stakeholders.

Selecting appropriate Scrum Master(s) and identifying relevant Stakeholder(s) is crucial to the success of any project. In some projects, there may have been pre-conditions stipulating certain team members and their roles.
When there is flexibility in choosing the Scrum Master(s), the following are important Selection Criteria:
1. Problem-solving skills—This is one of the primary criteria to be considered while selecting Scrum Master(s). The Scrum Master(s) should have the necessary skills and experience to help remove any impediments for the Scrum Team.
2. Availability—The Scrum Master should be available to schedule, oversee, and facilitate various meetings, including the Release Planning Meeting, Daily Standup Meeting, and other Sprint related meetings.
3. Commitment—The Scrum Master should be very committed to ensure that the Scrum Team is provided with a conducive work environment to ensure successful delivery of Scrum projects.
4. Servant Leadership Style- Servant leaders employ listening, empathy, commitment, and insight while sharing power and authority with team members. Servant leaders are stewards who achieve results by focusing on the needs of the team. This style is the embodiment of the Scrum Master role.
When identifying the Stakeholder(s), it is important to remember that stakeholders are all the customers, users, and sponsors, who frequently interface with the Product Owner, Scrum Master, and Scrum Team to provide inputs and facilitate creation of the project’s products. The stakeholders influence the project throughout its lifecycle.

 To know more click on:  http://www.scrumstudy.com/blog/

Responsibilities of the Product Owner in SCRUM

If you know Scrum/Agile then have you ever wondered if there is something called an Agile Product Manager? If you understand Scrum/Agile properly, you would realize that there is a role like that. But this role is defined as the Product Owner.  The Product Owner is very different from a traditional Project Manager. The role of Product owner may vary depending on the situation in hand but there are certain activities the Agile Project Manager (or Product Owner) must perform.

The Product owner is in-charge of the Project and is ultimately responsible for Project Success, to stakeholders and to the company. With so much pressure on shoulders, it is easy to revert back to traditional Project Management method. Hence, to make Scrum work, the Product owner needs to prioritize different activities and focus on ones that are really important.

Here, we will discuss few activities that a Product Owner should perform for a successful Scrum project. A Product Owner,

1. Creates and MAINTAINs the Product Backlog. Since maintaining is an on-going activity that is why I have put so much emphasis on it. Since things keep changing very fast, it is important for Product Owner to keep his eyes on the ball.

Note: In order for the team to remain productive, It is good to prepare the Product Backlog prior to the Sprint Planning meeting.

2. Prioritizes the Backlog for the best possible returns prior to the Sprint Planning Meeting (the Product Owner may refer to the various tools and books). Hence each user story must be sequenced depending its priority.

3. Conveys the Vision and Goals at the beginning of every Release and Sprint. This prevents the team from any kind of deviation and act as a benchmark for the team to measure their activity and progress.

4. Represents the customer, interfaces and engages the customer. The product Owner should always involve customer and stakeholder and give them a confidence that the right product is being built.

5. Actively takes part in the daily Scrums, Sprint Planning Meetings and Sprint Reviews and Retrospectives. There are always excuses to miss these meetings but it is an opportunity for the Product Owner to analyse the mistakes and implement the changes, which is the key to successful projects.

6. Always communicates status externally. The product owner represents the Team to the outside world and should make sure that all channels of communications are open and projects have the support required to succeed.

7. Terminates a Sprint if it is known that a major change needs to be implemented.

Being a Product Owner can be really burdensome. So choose your Product Owner wisely, cause he will be the one who will being success or failure to the project or rather company.

To know more: http://www.scrumstudy.com/blog/responsibilities-of-the-product-owner-in-scrum/