Time Management: Meetings & PTA-S

Time Management: Meetings & PTA-S
Yours Truly | November 2019

PTA-S =

  • Purpose
  • Time
  • Agenda
  • Summary

Scrum Master prepares a PTA-S before each Meeting
PTA = presented in 5 minutes at the beginning of the Meeting
S = presented at the end of the Meeting, time-box to 5 minutes/hour

Summary = Notes taken by the Scrum Master during the Meeting, when Agenda Items are discussed. Makes sure everyone is on par with what was discussed and potentially shareable with non-participants.

If anything come up that is not in the Agenda, take note of it in a Parking, to be discussed afterward.

Source = Michael de la Maza in “Robust Scrum Master Training” (Udemy)

https://www.udemy.com/course/scrum-master/

Key Findings from Cloud Leaders: Why a Cloud Center of Excellence Matters

AWS recommends a cloud center of excellence (CCoE) to address the added complexity. And as the report shows, IT and business operations leaders recognize the power of this best practice – even if they haven’t yet applied it.

“A Cloud Center of Excellence (CCoE) is a cross-functional team of people responsible for developing and managing the cloud strategy, governance, and best practices that the rest of the organization can leverage to transform the business using the cloud. The CCoE leads the organization as a whole in cloud adoption, migration, and operations. It may also be called a Cloud Competency Center, Cloud Capability
Center, or Cloud Knowledge Center. “ — Cloud Management Report 2017

Three key themes emerged from the report:

  1. The full potential of the cloud has not yet been realized
  2. Organizations adopting a CCoE for cloud leadership and vision
  3. Organizations benefit from a CCoE

Author = AWS Public Sector Blog Team

https://aws.amazon.com/blogs/publicsector/key-findings-from-cloud-leaders-why-a-cloud-center-of-excellence-matters/

Scrum Master Engagement Patterns: The Development Team

Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. Much to the surprise of many readers, the direct Scrum Master engagement with a single Scrum Team of average size and a typical 2-week Sprint turned out to be about 12 hours per week.

This result immediately prompted two additional questions: What are Scrum Masters doing during the rest of the week, and in what way does a Scrum Master’s work manifest itself over time? While answering the above question requires additional research and data collection, the latter can be answered to a certain grade by focusing on a few common scenarios.

The first article of this series will address the Scrum Master engagement with the Development Team.

Other content:
The Scrum Master Responsibilities According to the Scrum Guide
Scrum Master Engagement with the Development Team

(…) three main scenarios for the Scrum Master’s support of the team:
The Co-located, Stable Scrum Team Scenario
The Distributed Scrum Team Scenario
The Remote, Outsourced Scrum Team Scenario

Scrum Master Engagement Pattern—Conclusion

Author = Stefan Wolpers

https://age-of-product.com/scrum-master-engagement-patterns/

A Day in the Life of a Scrum Master

A great Scrum Master…

  • Ensures the entire team supports the chosen Scrum process;
  • Manages the impediments that exceed the self-organizing capabilities of the team and it prevents them in achieving the Sprint Goal;
  • Recognizes healthy team conflict and promotes constructive disagreement;
  • Is prepared to be disruptive enough to enforce a change within the organization;
  • Understands the power of a self-organization;
  • Understands the value of a steady sprint rhythm and does everything to create and maintain it;
  • Knows how to truly listen and is comfortable with silence;
  • Understands the strength of coaching and has learned some powerful questions by heart;
  • Teaches the Product Owner how to maximize ROI and meet objectives;
  • Is also competent with XP, Kanban and Lean.

A day in the life of a Scrum Master:

  • Start the day with an open and curious mind (and in my case some good coffee)
  • A good first question to consider is “How can I improve the live of the Scrum Team by facilitating creativity and empowerment?”
  • Remember: your agenda is as good as empty! Except for the Daily Scrum and maybe some other Scrum events
  • You attend the Daily Scrum as an observer. You listen to what is and isn’t being said.
  • You consider some of the questions I’ve mentioned earlier.
  • Based on your observations you determine your next steps. This might be coaching, consulting, teaching, facilitating, mentoring, managing, problem solving, conflict navigating or… just sitting with the team, listening and watching the team.
  • Doing “nothing” is a perfect activity for a Scrum Master! The biggest pitfall for a Scrum Master is being too busy and not noticing what is really going on.

Author = Barry Overeem

http://www.barryovereem.com/a-day-in-the-life-of-a-scrum-master/

What makes a good Scrum Master?

Here is what the Scrum Master is NOT:

  • Scrum Master is NOT a project manager
  • Scrum Master is NOT the boss
  • Scrum Master is NOT responsible for talking to stakeholders
  • Scrum Master is NOT the head that rolls in case of project failure
  • Scrum Master is NOT the person calling everyone to the scrum meetings

Here are 8 things that will benefit a good Scrum Master:

  1. Lots of experience! (Has done Scrum projects in the past)
  2. At ease with being inconvenient, annoying and a pita
  3. Ability to watch and listen
  4. No superior
  5. Servant leadership
  6. Empathy
  7. Communicative
  8. No fear (of superiors or being fired)

Author = Matthias Orgler (Hackernoon)

https://hackernoon.com/what-makes-a-good-scrum-master-fba685120534