Atlassian AfricaSouth Africa 2015

Jonathan Singh

• Intro & Context• Product Teams• Engineering Culture• Unified Platform : Jira and Confluence– Portfolio Backlog Prioritisation– Requirements Collaboration– Team Backlogs– Sprint Planning and Execution– Release Management– Incident Tracking

Agenda

Our Journey

• Channel UI : Web and Mobile • Channel Apps : eg VAS, Order Management

Application Context

• New Team Structure– Teams previously aligned to projects– Long Running Teams

• e.g. Platform, Banking, Wealth

• Triad Leadership– Product Manager– Technical Lead– Design Lead / QA Lead

• Multi Disciplined – Mobile : IOS, Android– Web , Angular JS– Java– Testers and BA’s embedded into teams

• Loosely coupled but closely aligned

Product Delivery TeamsTL

QA PO

Product Delivery Teams

BusinessProductTeam

SolutionEngineering

QA Business

TechLead

QALead

Product Owner

IterationManager

• 6 Product Teams• Global App, Multiple Platforms• Combined Monthly Release

• Discovery Backlog• Discovery• Inception• Team Backlog• Build and Test• Monthly Release

Product Delivery Cycle

How do we Align Product Teams to Product Delivery Cycle and to Monthly Releases ?

• Culture Drive: Its all about People !– Innovation, Agility, Responsiveness– Lean IT– Think MVP

• Unified Collaboration Platform

• Team Processes and Values ~ Christensen– Influence Culture– TDD, CI, Modularity

Agile Engineering Culture

“CULTURE EATS STRATEGY FOR BREAKFAST.~ PETER DRUCKER

• Portfolio Backlog Management• Requirements Collaboration• Team Backlogs , sprint planning and execution• Continuous Integration• Release Management• Traceability• MIS

• Atlassian Tool Suite as a unified platform to bring Business and IT together

Unified Platform Multi Disciplinary Teams

• Confluence Story Template

• Customised Jira Project– Fields : teams, region– Workflows : epics, stories, incidents – Screens

• Kanban Portfolio Backlog– Aligned to product delivery cycle– Product Team Filters

• Track Epics per product team• Scrum or Kanban boards per team

• Releases– Monthly, small increments

Unified Platform Tooling Jira and Confluence

Unified Platform Portfolio Backlog

• Weekly prioritisation session

Unified Platform : Screens

Unified Platform : Screens

Unified Platform : Teams

• User Stories , Confluence – UX Designs– Business Requirements– Acceptance Criteria– Contracts– Page History– Stories linked to Epics • Jira Epic and Story

Unified Platform Requirements Collaboration

• Team Boards aligned to Jira Board

Unified Platform : Team Backlogs

Unified Platform : Team Backlogs

• Each Team has its own boards to track Stories , Bugs, Incidents and Tasks• Common underlying Jira Project

Unified Platform : Team Iteration Planning

• Multiple Contributing Teams– Development in Trunk– Release code and stabilise : 2-3 week Cycle– Monthly Release Trains– Train leaves the station– Feature Toggling– Beta– Market Release, Business pulls the Trigger

• Jira Road Map and Release notes

• Kanban Release Board

Release Trains

Release Trains

• Confluence Landing Page : Create Incident against respective team

Incident Tracking

Incident Tracking

• Jira Portfolio– Licences Procured

• Jira REST API– Reduce handoffs

• Reporting

• Dev Ops : Afternoon Slot

Next Steps…

• Lean IT – Mary Poppendieck– https://www.youtube.com/wa

tch?v=ugdu1YngE9w

• Scaled Agile– SAFE Framework– http://www.scaledagileframew

ork.com/

• Product Delivery– Marty Cagan– https://www.youtube.com/wa

tch?v=734K7cEo30U

• Continuous Delivery – Jez Humble– https://www.youtube.com/wa

tch?v=IBghnXBz3_w

References and Credits

• Release Engineering– Google, Chuck Rossi– https://www.youtube.com/watch?v=Nffzk

kdq7GM

• Engineering Culture– Spotify– https://vimeo.com/85490944

• MVP , Agile Coaching– ThoughtWorks

• Collaborative Tooling– Atlassian

• Architecture , Infrastructure, Configuration– Standard Bank