Scaling Atlassian for the Enterprise

Editor's Notes

1. Now that we know how communication flows, lets see some more details on what happens at each level from concept to delivery First – there is an idea generation and there is an intake funnel which can be in JIRA , Confluence or some other enterprise tool. Once these ideas are vetted through economic and business viability, the approved initiatives flows through the program level. Next – your program teams break those initiatives into features, establish dependencies, and plan releases. This plan maps to the team’s backlog. Finally – teams are focused on development and delivery Lets take a closer look at each of these.  
2. So lets first take a look at the Portfolio Teams. Their main goal is to view, plan, and track all important initiatives. So what are they are doing to achieve that goal? They are going to look at where we are in the process, are we focused on the right things…….and they’ll need to under the impediments. Lets go take a look on how they will perform few of these activities. So we looked at the overall health of our initiatives. Any questions? john/cprime Admin/Charlie! Capabilities Kanban boards WSJF calculation , strategic themes, and prioritization Open link to share to linked features, Confluence documentation, hipchat integration Dashboards As a Portfolio Manager, my goal to understand progress or health of our  portfolio To do this, I’ll need to view where we are in the process of delivering our intiatives, confirm we are working on the right things (bang for our buck) , delve into details and view features for an initiative and determine if what we are working on is aligned with our strategic themes.  All this will be need to be communicated to the Program Team. From this view , I can see what initiatives we have in play.   I’d like to focus on our most important strategic theme, which is XYZ so I’ll filter my view to focus on those initiatives. I want  to know if we are ready to move the next initiative to approval but I see that we are past our WIP.  Taking a look at the items in bottleneck, I decide to re-rank so we can focus on most important and move them to the next phase.{covered Kanban board, WIP limit, , filter by them, capturing process (workflow) …} To summarize, as a Portfolio manger, I’ve been able to get view into my portfolio by seeing where we are in the process of delivering, identify any bottlenecks, look at details down to feature level. All this information helps me make better decisions on the priority of the work.
3. Next lets take a look at our program Teams. Their main goal is to coordinate activities and to ensure the delivery of the release. So what are they are doing to achieve that goal? They are going to look at where we are in the process, are we focused on the right things…….and they’ll need to understand the impediments. Lets go take a look on how they will perform few of these activities. So we looked at the overall health of our features. Any questions? Capabilities Kanban boards – WIP limit and flagged issues Open issue to view linked issues, dependencies, more feature breakdown Open Structure – see where it is in overall priority, what teams are working on it, progress Tempo Program board to see if feature is at risk, sprint timeline, overall capacity report Tempo Folio to plan resources for a release – scope, budget, costs Program Dashboard for additional metrics
4. Next lets take a look at our product teams. Their main goal is to coordinate activities and to ensure the delivery of the release. So what are they are doing to achieve that goal? They are going to look at their backlog, prioritize and groom it, and manage dependencies. Lets go take a look on how they will perform few of these activities. So we looked at the overall health of our features. Any questions? Capabilities Scrum boards with epics and stories aligned next to each other, Drag&Drop to prioritize, start a new sprint Look at reports on how epics are burning down (Feature 20) along with projected completion of epics Look at reports on how release is burning down (WDP Greencloud new web page) As a Product Owner my goals is to ensure timely release.  My main activity is grooming the backlog so the team knows what to work on.  To do this, I'll be  ranking the backlog, communicating the details of the backlog, ensuring  dependencies are met, determine team’s availability, confirm we can meet our release date.
5. Next lets take a look at our delivery teams. Their main goal is to track and manage sprint commitments for optimal delivery. So what are they are doing to achieve that goal? They are going to look at their workboard, prioritize and groom it, and manage dependencies. Lets go take a look on how they will perform few of these activities. So we looked at the overall health of our features. Any questions? Capabilities Work board to track current sprint activities - Drag and drop activities across columns Track team’s velocity and sprint reports Team timesheets Tempo planner to track team’s capacity Team Dashboard
6. Next lets take a look at our delivery teams. Their main goal is to track and manage sprint commitments for optimal delivery. So what are they are doing to achieve that goal? They are going to look at their workboard, prioritize and groom it, and manage dependencies. Lets go take a look on how they will perform few of these activities. So we looked at the overall health of our features. Any questions? Capabilities Work board to track current sprint activities - Drag and drop activities across columns Track team’s velocity and sprint reports Team timesheets Tempo planner to track team’s capacity Team Dashboard