Showing posts with label scrum master. Show all posts
Showing posts with label scrum master. Show all posts

Saturday, June 08, 2019

Scrum Master Role & Responsibilities (Courtesy Roman Usov)

Use the following as a checklist when transitioning to a new team

Start by asking the Team -- "What do you expect from me?" (This is basically setting the expectations and ensuring both are on the same page)

Team
- Be the mirror
- Ask a lot of questions
- Observe (events,  relationships, processes, people, check team's profiles on social networks)
- Observe team dynamics during Scrum events
- Learn about team values, conventions and agreements
- Ask what I can help the team with (maybe, as an activity at a retro, what, why)
- Find small things to help the team with
- Suggest a couple of get-to-know activities for a retro ('get to know you' quiz, journey map, team canvas), learn about team expectations, find an opportunity to tell the team about how I view my role
- Go to lunches with the team
- Provide welcome treats
- Seek opportunities for one-on-ones (at coffee, at lunch)
- Have a trip to meet guys working from another office
- Learn about interactions and dependencies outside the team
- Learn about team's improvement backlog
- Notice deviations from the Scrum Guide
- Notice problems that can be helped with Scrum
- Ask questions about what I see, offer observations for issues and draw team's attention to them where appropriate, ask to ponder ideas
- Notice what team is struggling with, suggest observations, stories from experience
- Review available team artifacts and metrics

Processes & Tools
- Learn about team's development process
- Learn about CI and deployment process
- Learn about tools used by the team

Product
- Learn about product
- Review product backlog
- Learn about current PBR process

Organization, culture (what's important and why, how we do things here and why), environment
- Learn about mission, vision, strategy
- Learn about values, observe if they are really lived by
- Learn about structure, key components and interactions
- Notice problems that can be helped with Scrum
- Attend community of practice meetings

Stakeholders
- Learn about key stakeholders
- Find opportunities to meet with key stakeholders
- Learn about stakeholder needs and expectations

From Chandan Lal Patary
===================
- Enables the team to eliminate impediments
- Coaches team in scrum practices
- Protects team from external intervention
- Has continuous improvement mindset and practices it
- Is an outstanding facilitator
- Is a servant leader
- Has good influencing skill
- Knows the domain and technology
- Has substantial organisational skills
- Is an outstanding communicator
- Is an excellent conflict manager
- Capable of building self-organised team
- Has good collaboration skills
- Builds transparency into the team

Wednesday, December 19, 2018

Key Agile Topics

Scrum Master
============

1.The purpose of top level scrum ceremonies
2.The value of observed practices during ceremonies
3.Resolve impediments external to the team
4.Write deliverable, vertically-sliced stories
5.“Turn up the good” through frequent retrospectives
6.Make work visible
7.Promote a psychologically-safe team environment
8.Model servant leadership behaviors

Product Ownership
==================

1.Product Manager / Analyst Role Evolution
2.Product Ownership
3.Customer Experience
4. NFR Overview
5. NFR Considerations
6.The Backlog
7.Value / Return on Investment
8.Technical Debt
9.Market Analysis
10.Product Design
11.Product Marketing Basics
12.Business Value Domain
13.Embedded End User Feedback

Agile Leadership
================

1. Team composition
2. Product ownership
3. Portfolio management / work intake
4. Customer experience
5. IaaS
6. Legacy system evolution
7. NFR and considerations
8. Talent management
9. Vendor management
10. Financial management
11.Dependency Elimination

Visualizing Next Word Prediction - How to LLMs Work?

 https://bbycroft.net/llm