Skip to end of banner
Go to start of banner

Kitfox - Brainstorming - How to reduce context switching

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

How does this project fit with the strategy?

Status

ACTIVE / INACTIVE / SHIPPED


Problem space

Why are we doing this?

Problem statement

High level of context switching to ongoing activities

Impact of this problem

Team capacity available for automation tasks

How do we judge success?

70% of capacity is used for CI/CD automation

What are possible solutions?

  1. Create schedule duty for support activities.
  2. Create single channel for requests to Kitfox team.
  3. Regular education session for development teams once per sprint. (How to get secrets at rancher?)
  4. Record Q&A sessions. Keep agenda and discussed situations outlined
  5. Check and renew access to AWS Logs and educate TLs how to find debug info with help of CloudWatch
  6. Be ready to support new functionality beforehand by information from SAs, TLs.
  7. Engage teams to create jiras with full description
  8. Proper log aggregation to ElasticSearch and Kibana 

Validation

What do we already know?

What do we need to answer?

Ready to make it

What are we doing?

Why will a customer want this?

Visualize the solution

Scale and scope


Learn more: https://www.atlassian.com/team-playbook/plays/project-poster

Copyright © 2016 Atlassian

Creative Commons License
This work is licensed under a Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License.

  • No labels