Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

  • Core hours – times during the day that all Team members agree to be present and available for collaboration

  • Daily Standup – the time that it happens and what to do if you realize that you can’t make it that day

  • Cell phones – if or when it is appropriate to use them during Team events

  • Headphones – when it is fine to use headphones, versus when Team members will not use them so they’re available to communicate and collaborate with others

  • Product Owner – availability and contact information

  • Definition of ‘Done’

  • How the Team limits Work In Progress (i.e. the Kanban Concept)

  • How the Team ensures everyone has an equal voice and feels respected

  • If you miss a meeting or event then you agree to support decisions made in your absence.

  • If you can’t attend a Team event you will let the Team know in advance.

  • During each Sprint, at least one Team Member will work on growing a skill outside of their core strengths.

  • In the case of software development, every Sprint the Team will make an effort to improve some part of their code base.

  • Don’t be afraid to ask for help

  • Product Owner is available during core hours

  • Be on time for meetings

  • Tell the truth

  • Communicate individual schedule

  • ALL changes to the Sprint / Backlog must be approved by the Product Owner

  • Use the Impediment Backlog (or swimlane) for blocked issues

  • Define and adhere to ‘DONE’ criteria for stories

  • Define and adhere to Version Control rules

  • Adhere to code documentation standards

  • Update Backlog before Standup daily

  • Respect your team member’s time

  • No labels