Scrum-and-XP-from-the-Trenches#08: Distributed Teams & Scrum Master Checklist

In this session we will cover the following:

PART SIXTEEN – How we handle geographically distributed teams

  • Distributed teams
  • Communication bandwidth in a wider sense
  • Some Implemented Measures
  • Offshoring
  • Team members working from home

PART SEVENTEEN – Scrum-master checklist

  • Beginning of sprint
  • Every day
  • End of sprint
  • Try to make yourself redundant

Thank You and always keep it simple & straightforward 🙂

Advertisements

Scrum-and-XP-from-the-Trenches#07: Handle Multiple Scrum Teams

In this session we will cover the following:

PART FIFTEEN – How we handle multiple Scrum teams

  • How Many Teams to Create?
  • Virtual Teams
  • Super-Team or Dynamic Sub-Teams
  • Optimal Team Size
  • Synchronized Sprints – or Not?
  • Why we introduced a “team lead” role
  • How we allocate people to teams
  • Specialized teams – or not?
  • Rearrange teams between sprints – or not?
  • Part-time team members
  • Scrum-of-Scrums
  • Firefighting Teams (Support)
  • Splitting the product backlog – or not?
  • Code Branching – Important Lessons Learned
  • Multi-Team Retrospectives

Next session isA, we will talk about:

  • PART SIXTEEN – How we handle geographically distributed teams
  • PART SEVENTEEN – Scrum-master checklist

Thank You and always keep it simple & straightforward 🙂

Scrum Wiki

ScrumWiki is my own developed tool that used for communicating the Sprints Info Details among the company.

ScrumWiki simply displays the current running sprint details, It took from me about 40 hours during 3 weeks to finish developing it using MVC with Entity Framework.

ScrumWiki is open source & you can Clone it from Github using the following URL:
https://github.com/HossamHassan47/ScrumWiki.git

Sprint Info Details

  • Sprint Goal
  • Sprint Backlog
  • Sprint Schedule
  • Sprint Team

Running Sprints.png

Man of Sprint

This feature developed mainly to encourage the competition among the Scrum Team.
The best performance team member during the sprint will be the Man of Sprint.

Man of Sprint.png

Admin View

Manage Projects (Add, Edit, or Delete)

Manage Projects.png

Manage Sprints (Add, Edit, or Delete)

Manage Sprints.png

Manage Product Backlog Items (Add, Edit, or Delete)

Manage Backlog.png

Manage Sprint Team Members (Add, Edit, or Delete)

Manage Sprint Team.png

Manage Team Members (Add, Edit, or Delete)

Manage Team Members.png

Manage Roles

Manage Roles.png

Thank You and always Keep It Simple & Straightforward.

Scrum-and-XP-from-the-Trenches#06: Testing

In this session we will cover the following:

PART FOURTEEN – How we do Testing

  • You probably can’t get rid of the acceptance-test phase
  • Minimize the acceptance-test phase
  • Increase quality by putting testers in the Scrum team
  • What does the tester do when there is nothing to test?
  • Sprint cycles vs. acceptance-test cycles
  • How do we deal with reported bugs?
  • Alleviating the Testing Bottleneck

Next session isA, we will talk about PART FIFTEEN – How we handle multiple Scrum teams

Thank You and always keep it simple & straightforward 🙂

Scrum-and-XP-from-the-Trenches#05: Release Planning & Scrum with XP

In this session we will cover the following:

PART TWELVE – How we do Release Planning and Fixed-Price Contracts

  • Define your Acceptance Thresholds
  • Time-estimate the most important items
  • Estimate Velocity
  • Put it Together into a Release Plan
  • Adapting the Release Plan

PART THIRTEEN – How we combine Scrum with XP

  • Pair programming
  • Test-driven development (TDD)
  • Incremental design
  • Continuous integration
  • Collective code ownership
  • Informative workspace
  • Coding Standard
  • Sustainable pace/energized work

 

Next session isA, we will talk about PART FOURTEEN – How we Do Testing.

Thank You and always keep it simple & straightforward 🙂

Scrum-and-XP-from-the-Trenches Session#02: Sprint Planning

In the last session, we covered part 1 and 2 from the book. We talked about the basic requirements for Scrum and how to make the product backlog. You can check it from the following link:

Scrum-and-XP-from-the-Trenches Session#01: Intro & Backlog

In the 2nd session, we will cover the following:

PART THREE – How we prepare for sprint planning

PART FOUR – How we do sprint planning

  • Sprint Planning Meeting Purpose.
  • Sprint Planning Meeting Concrete Output.
  • Why the product owner has to attend?
  • Why quality is not negotiable?
  • Sprint-planning-meeting agenda.
  • Defining the sprint length and goal.
  • Deciding which stories to include in the sprint.
  • How can product owner affect which stories make it to the sprint?
  • How does the team decide which stories to include in the sprint?
  • Why we use Index Cards?
  • Definition of “Done”
  • Time estimating using Planning Poker
  • Clarifying Stories
  • Breaking down Stories into Smaller Stories
  • Breaking down Stories into Tasks
  • Defining Time and Place for the Daily Scrum
  • Tech Stories
  • Bug Tracking System vs. Product Backlog
  • Sprint Planning Meeting is Finally Over!

Next session covers the following:

  • PART FIVE – How we Communicate Sprints
  • PART SIX – How we do Sprint Backlogs
  • PART SEVEN – How we Arrange the Team Room
  • PART EIGHT – How we Do Daily Scrums

Scrum-and-XP-from-the-Trenches Session#03: Sprint Backlog & Daily Scrum

Thanks and Keep it simple & straightforward 🙂

Scrum-and-XP-from-the-Trenches Session#01: Intro & Backlog

Within our knowledge transfer activities that held up in the team, I’ve been asked to prepare a session about Scrum so that the whole team can get familiar with Scrum and be able to apply it.

I decided to talk about Scrum via a book called Scrum-and-XP-from-the-Trenches by Henrik Kniberg. It’s a free book and you can download it from here.

This book includes:

  • Practical tips and tricks for most Scrum and XP practices
  • Typical pitfalls and how they were addressed
  • Diagrams and photos illustrating day-to-day work
  • Testing and test-driven development
  • Scaling and coordinating multiple teams
  • Dealing with resistance from inside and outside the team
  • Planning and time estimation techniques

We already had 8 sessions that cover this book from start to end. I told myself why not make those sessions public and share them with you hoping that it may help you to start applying Scrum in your team.

In our first session we will cover the following:

  • Basic requirements for Agile iterative development
  • Teams need to know Scrum basics
  • The Nokia standards for Scrum
  • Focus on Getting Things Done
  • PART ONE – Intro
    • What is Scrum?
  • PART TWO – How we do product backlogs
    • Stories Main Fields
    • Additional Story Fields
  • How we keep the product backlog at a business level

About the book Author

Agile and Scrum Basics

Nokia Standard for Scrum

Getting things Done

Content

What is Scrum

Product Backlog

Story Main Fields

Story Additional Fields

Keep Backlog at Business Level

Slide Share

Full Video

Next session covers the following:

  • PART THREE – How we prepare for sprint planning
  • PART FOUR – How we do sprint planning

Scrum-and-XP-from-the-Trenches Session#02: Sprint Planning

Thanks and always keep it simple & straightforward 🙂