Mar 23
Agile Working Agreement

Below is an exmaple I created for my Agile development team that includes a working agreement and various definitions.  Hoep this helps as you adopt your own Agile methodologies. 

Working Agreement and Definitions

Success is measured at the team level and as a team we succeed and fail together.

Each Developer is responsible for their own work.

Working Agreement

  • All members of the development team will be present for the daily scrum.
  • Story points are used for estimation.
    • Story Points 4-5 should be broken up.
  • JIRA should be utilized fully for issue tracking.
    • Indicate which issues you’re working on by moving the cards through the JIRA workflow.
    • If waiting on a client to get back with feedback flag the issue - COMMENT
    • Log work done daily on any issues you’re working on.
    • Ensure all issues that are done are closed out before the end of a sprint.
  • Unit, integration and functional tests should be added to cover new functionality.  This is even more of a concern when performing a bug fix on an existing piece of code.
  • Unit and integration tests will be ran before checking into the version control system.
  • Code should be checked into version control as often as possible but at least once per day.
  • Code APIs should be well documented.
    • Indicate what arguments are brought in and the format they’re expected to be in.
    • Indicate what data gets returned.
    • Indicate what kinds of errors can be expected.
  • Code should be high quality.
    • Code-related issues which should be cleaned up before check-in.
    • Code should be warning free unless clearly documented.
  • Use chat channels for questions/input whenever possible with a preference for the cross-team chat channels.

Definition of Ready

  • User Story written well, high level "As X, I want X, So that I can X", this may include business rules.
    • Developers create technical specs from the User Story and Business Rules.
  • Development timeline fits within the sprint.
  • Test cases and Stakeholder testing can be accomplished within sprint.
  • Story Points assigned.
  • Time estimate assigned.
  • Work to be done must be clear (Minimize scope creep)
  • Acceptance Criteria defined.
    • Varies based on the sprint and work expected.
    • The Stakeholders and PO can revisit this to ensure success.

Definition of Done

  • Testing has been completed and validated by peers.
  • Changes have been applied to all code instances (Snd, Dev, Tst).
  • Documentation updated.
  • UI tested in all major browsers (Chrome, IE 9-current, Firefox, Safari, iOS).
    • This includes Mobile.
    • Document cases where it is not mobile.
  • All code changes have been deployed to the Test instance as well as indicated in the JIRA workflow.
  • Performance has been tested and all pages load within 2 seconds; this is standard practice.
  • All Acceptance Criteria met.
  • UX tested by major stakeholders (branching logic, order of tests, etc), intuitive interface.

Backlog Refinement

  • PO has met with Stakeholders.
  • PO and Scrum Master have talked.
  • Stakeholders Business Rules are clear and concise enough to prioritize.
  • Development team has written the technical specifications based on Business needs “rules”.
  • Team participates in discussion after backlog has been sufficiently vetted by PO, Lead, Management, and Stakeholder.
  • Discuss Testing checklist with developers.
  • Is the new task “Ready for play”?

Retrospective

  • Discuss wins and improvements.
  • Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
  • We now know more than we did previously; let's celebrate this gained wisdom!
  • http://www.retrospectives.com/pages/retroPrimeDirective.html

Ceremony "Stakeholder Infoshares"

  • Discuss with team and stakeholders improvements and changes.
  • Discuss wins and improvements and how we can better succeed.

 

Comments

There are no comments for this post.

 ‭(Hidden)‬ Blog Tools