User Tools

Site Tools


This is an old revision of the document!

Self Managing Teams

  • Team informs the product owner that something might take longer due to changing requirements
  • Don't let the customer dictate the solution. Let them give requirements and let the team come up with the solutions
    • One approach is to rotate the role of scrum master.
  • Wasn't the best approach. But the scrum master does need to go on vacation, so having a replacement ready is important.
  • Roles shouldn't be rigidly defined. Better to get in a room together and come up with solution collaboratively.
  • Code reviews for each story help with diversification and knowledge sharing
  • Create a 2 or 3 hour task or story for cross training
  • Pairing can share knowledge and reduce bugs.
  • Less role clashes when moving to Agile, more personality.
  • Adding Agile Practices as a category of the review can help boost Agile adoption.
  • Getting other departments to jump to Agile helps boost adoption for the whole organization When interfacing with third parties, you may have to synchronize development cycles
  • Don't rely on third party mediation. Try to solve issues internally
  • Team working agreement or Ground rules ‐ “How are we going to work together”.
    • A sort of policy that only applies to the local team.
    • Intended to handle activities or points of contention and involves over time
selforganizingteams.1404757261.txt.gz · Last modified: 2014/07/07 11:21 by admin