Skip to content

Instantly share code, notes, and snippets.

@barberj

barberj/scrum_charter.md

Last active October 6, 2015 14:17
Show Gist options
  • Save barberj/f5487b90889b47f93a04 to your computer and use it in GitHub Desktop.
Save barberj/f5487b90889b47f93a04 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
scrum_charter.md

We few developers of SalesLoft, in Order to form a more perfect Platform, do ordain and establish this Charter for the Gainmakerz of SalesLoft.

Challenge

  • We challenge ourselves to make gainz from features and services not yet realized, from the betterment of existing features and services and the extermination of bugs.

Gainz

  • We find the most gainz occur between the hours of 9-5. As such that is when we will conduct regulated business.
  • We find that gainz can happen anywhere and often are a catalyst of environment changes. As such we are open to WFH so long as it does not conflict with requests requiring XP efforts. We are open, but acknowledge that abscence does not necessarily make the heart grow fonder, but rather weakens the bonds of culture. To this point we will also gather offsite monthly to strengthen Team culture and achieve ultimate gainz.

Review

  • We strive to complete reviews within 4 business hours. To clarify the necessary from the commentary our reviews will include a summary explicitly stating issues needing remediation. Remediation should occur within 4 business hours.
  • XP efforts still require review. Given the nature of XP and the in-herent code quality gainz the review should be more focused on achieving core business objectives.

Requests

  • To ensure the utility of gainz, requests should be specced to the full extent possible given the urgency and nature of the request. Expedited requests will be worked immediately following the conclusion of current gainz if current gainz are achievable within reasonable time. XP efforts should not be stopped if possible to work on an expedited request.

Engagements

  • Team members will participate in stand-ups on a daily basis and retros on a weekly basis. If unable to attend an email or slack message should be sent to the Team. Present members in the ceremony will read missing members' communications. We realize sometimes communication is not possible and we agree that should a missing member be unable to communicate; we will reach out for the pertinent information and state and well being of the missing member.
  • All engagments must have a clearly defined objective.

Accountability

  • We strive to ship first gainz by Friday, worst case Monday.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment