Notes from 70 Scrum Master Theses

 Notes are from here. 


- Every "good practice" must be tailored to context.

- Scrum Master should never act as enforcer 

- Product backlog includes user stories, bugs, spikes, and non-functional requirements

- A Product Backlog is “actionable” if the Scrum Team can organize a successful Sprint Planning at a moment’s notice.

- Incomplete and poorly prepared work items seriously hamper the effectiveness of a Scrum Team. These items should never be selected for the Sprint Backlog, but instead sorted out during Product Backlog refinement meetings.

- Daily Scrums cannot fix — and is not supposed to fix—, among other things: a dysfunctional organization, a dysfunctional Scrum Team, an inadequate Product Backlog, a Sprint Planning session gone wrong, low-quality user stories, or a missing product vision.

- All issues, concerns and frustrations, should be documented — even if just temporarily using sticky notes. Though it’s always better to keep a formal document or file. (Limit access to these documents to the Scrum Team members, though.)

- Reasons typically given by management for transitioning to Scrum and other agile practices include: Making the organization more efficient; Helping the organization deliver faster; and Improving the predictability of delivery dates. Organizations making the switch to Agile must be clear on their "why" for adopting the new framework. 

- A successful transition to Scrum requires the backing of C-level executives; a bottom-up approach is futile.

- Be wary of Scrum anti-patterns (patterns that do not align with Scrum). 


Comments

Post a Comment

Popular posts from this blog

XP: Card, Conversation, Confirmation - The three C's

Image
  This is a technique lifted from XP (Extreme Programming).  Card On each card is enough text that identifies a requirement. Notes of priority and cost are written on it as well. They serve as tokens for requirements and are handed to developers during implementation and returned to customers when completed. Conversation  Conversations are collectively exchanges of thought between customers and programmers. It is largely verbal, but may be communicated with supplemental examples. Confirmation Confirmation, in other words, acceptance tests, are defined at the start with the customer and shown to customer at the end of the iteration to confirm the story's completion. Note that extra documentation, while seemingly helpful, hardly "confirms" anything and cannot replace acceptance tests. 
Read more

Notes: 10 Knowledge Areas of Project Management (PMBOK 6)

Image
 Notes from here  There are 10 knowledge areas, as outlined in PMBOK 6, that are to be remembered sequentially. It is presented in logical order (with exception to Stakeholders which is tacked on at the end).  Integration: In other words, you can’t ‘do’ schedule management and ignore what the impacts of that might be on people, risk, communications, cost and the rest. Scope: Knowing what the project will deliver Schedule: all about making a detailed plan to tell everyone when the project will deliver what is in the requirements. Cost: Managing project fund Quality: Although quality varies project to project and many aren't as regimented, it is important to be aware and use appropriately Resource: Working out the resources needed to get the project done Communication: Creating a communication plan and monitoring for adjustments Risk: Covers an adequate overview of managing risks  Procurement: Depending on any purchases involved, there is a lot of contracting and negotiation Stakehol
Read more

RACI Definitions

Image
Notes from site RACI is a matrix to properly organize and define stakeholders' responsibilities in the project. While there are many methods in creating these organizations, this is just one method. Definitions should be kept nearby and the charts should be clear.  Responsible: This team member does the work to complete the task. Every task needs at least one Responsible party, but it’s okay to assign more. Accountable: This person delegates work and is the last one to review the task or deliverable before it’s deemed complete. On some tasks, the Responsible party may also serve as the Accountable one. Just be sure you only have one Accountable person assigned to each task or deliverable. (Note: It might not be your PM!) Consulted: Every deliverable is strengthened by review and consultation from more than one team member. Consulted parties are typically the people who provide input based on either how it will impact their future project work or their domain of expertise on the del
Read more