"Atlassian Tools and Practices to help your teams Get Shit Done!". As the title suggests, the objective was to introduce attendees to Atlassian Team Playbooks, Health Monitors, and the tools including Confluence, Jira, Status Page, Trello, Bitbucket, and Bamboo.

Pre-requisites

• An instance of Jira Software, Confluence, Bitbucket, and Bamboo (integrated with each other)
  
• Confluence installed with Team Playbook add-on (Project Poster and Project Team Health Monitor)
  
• Accounts for each team to log in and create content
  
• You will also need a repository in Bitbucket that is integrated with Bamboo that deploys to a web server or an S3 bucket where you can access an HTML page deployed
  

Agenda

1. Team Breakouts (45Min)

Break out into different teams. I suggest a team of 6 to 8 members. Each team will be provided with a copy of the following:

• Login instructions to the instance
  
• Print-out of the Atlassian Project Team Health Monitor (download here)
  
• Print-out of the Atlassian Team Playbook Project Poster (download here)

2. Team Health Monitor (45 minutes)

• Purpose of the Team Health Monitor.
  
• A preview of how to create a page in Confluence using the Health Monitor Blueprint.
• Each team to discuss 2 or 3 attributes.
• Document in Confluence.

3. Project Poster (45 minutes)

In this section, we will be providing three strategic objectives for all teams. Each team will be responsible for coming up with a new feature to existing Atlassian Products, or a new product. The feature or product should align with any one of the strategic objectives provided.

For example:

• Collaboration
  
• ITSM
  
• Developer Productivity
  

Each team will be responsible for coming up with a new feature or product, that aligns with either Collaboration or ITSM or Developer Productivity.

You will use Project Poster to brainstorm the idea, and answer two questions:

• What are we doing?
  
• Why will a customer want this?
  

The team will create a Confluence page using the Project Poster Blueprint, and answer the above questions in the "Ready to make it" section of the project poster.

4. Products Demo & Overview (120minutes)

• Jira
  
• Confluence
  
• Slack
  
• Trello
  
• BitBucket
  
• Bamboo, Crucible, and Fisheye
  
• Atlassian Marketplace
  
• Statuspage
  
• Sourcetree
  
• Crowd
  

5. Tracking Epics, Stories in Jira Software (45 minutes)

Each team will create an Epic in Jira, that is linked to the Project Poster page in Confluence. Each team will also move it to In Progress state and assign it to a developer.

6. Code in Bitbucket and deploy in Bamboo (45 minutes)

Note: This section needs additional setup.

Developers in each team will clone the repository, and create an HTML page to market their new feature or product. Upon commit, the repository is built and deployed to an accessible web server or an S3 bucket.

7. Demonstration and Wrap-up (60 minutes)

Each team demonstrate their published HTML pages, or simply read out their project poster section answering the key questions of what they are doing, and why will a customer want this.

 How plays like project poster benefit teams by establishing a shared understanding.