1. Goals
1.1. Set up a few simple patterns that we can all use in JIRA
1.2. With those patterns, support visibility and alignment
1.2.1. Keep it simple but effective
1.2.2. Do a better job of letting the tools do some work for us
2. How it works
2.1. Boards, Tasks, Workflows
2.1.1. Code tasks and Non-code tasks
2.1.1.1. Simple. As close to an index card on a wall as we can get in JIRA.
2.1.1.2. Slightly different behaviors
2.1.1.3. Conducive to having a whole team's work on one board, that anyone can see, anytime, from anywhere.
2.1.2. Workflows
2.1.2.1. Flexible - several options already set up, and I am adept at rolling out new ones. Let's talk about what best suits your team's flow!
2.1.2.1.1. Some examples:
2.1.3. Release Log (Sample)
2.1.3.1. https://leadpages.atlassian.net/wiki/display/~dylan/Sample+Release+Log
2.1.4. No matter the workflow, important pieces to remember:
2.1.4.1. If you are working on something, or about to work on something, make sure there is a ticket for it
2.1.4.1.1. Keep the tickets simple
2.1.4.1.2. Try to write in "plain English" wherever possible
2.1.4.1.3. Keep your tickets up to date
2.1.4.2. If you are clearing a Bug or Code Task ticket off the board without completing it
2.1.4.2.1. Use the "Close without Completing" workflow step
2.1.4.3. Only move a Code Task or Bug ticket into the final column/step after it has been successfully deployed
2.1.4.4. Use the Release button to package up tickets for Released work and move them off the board, right after the deployment has been confirmed
2.1.4.4.1. Also adds them to the Release Log
2.2. The most important piece
2.2.1. Everyone owns the information and communication for their own pieces of work!
2.2.1.1. Many hands make light work.
2.2.1.2. Accurate info = Highly Valuable Views
2.3. Visibility and Alignment gains
2.3.1. Within each Product Delivery team
2.3.2. Between Product Delivery teams
2.3.3. For Product Delivery leadership
2.3.4. For Customer Success team
2.3.5. More?