Scrum master role for project.
1. Observe.
Try to observe and actively listen and take notes on their activities, strengths and weakness and
keep a note of them.
2. Learn about the product or the deliverable or the requirement.
Try to learn their products from the PO or management or stake holders and the teams working
on those products and how are they related to my team in terms of dependency.
3. Learn the workflow of the team.
Origination of work, stake holders who are responsible for my teams work and how the team
works. Dependency on any other team or teams. POC of those teams. The process of handover
of work and communication methods. This will help in clearing road blocks and bottlenecks.
4. What type of work the team is going to work on? PS, AM, Bugs or defects etc.




TO DO- New User stories or US from incidents or existing back log.
IN PROGRESS. - User Story in progress in terms of dev
IN REVIEW. Defects from QA perspective
DONE. Once the US is completed.
Core Metrics to be utilized for the team activities and used for the team.
1. Velocity: Plan and forecast product releases and milestone delivery by taking the throughput of
the team vis a vis time.
2. Capacity: Identify how much scope the scrum team should accept for every sprint.
Factors like, OOO, Buffer, Sprint activities like sprint retro and the sprint planning, Sprint
reviews, Backlog refinements, Enterprise activities
3. Burndown Chart: This will show the progress and work left for an active sprint or the project.
MPSA
6 rules of Kanban for Dev activities.
1. Visualize (the work, the workflow, and the business risks)
2. Limit Work in Progress (WIP)
3. Manage flow
4. Make policies explicit
5. Implement feedback loops
6. Improve collaboratively, evolve experimentally