Methodology

The details of how the team works together to deliver will depend heavily on the team, but most teams will tend toward Scrum, at least as a starting point.

It is important to understand that the purpose of a team using a methodology like Scrum is for each team to use it as a lens to inspect in order to adapt and remove impediments to success.

Learning to understand and apply a methodology (or set of principles) takes effort and time to learn to do well, and it's very important that we do not confuse following ceremony with following a methodology.

Having a backlog, sprints, daily stand-ups, and retrospectives does not mean we are using Scrum. All of these things must be done intentionally and used effectively to provide real value.

While we certainly want consistency in ability to deliver quality software and WOW our customers, the goal is never to have all teams working exactly the same way.

The following pages in this section are meant to describe some good defaults, but your team should take what works, drop what doesn't and continually adapt toward being more effective together and ensure you are prioritizing delivering value and quality to your clients over ceremony.