Kitfox - Brainstorming - How to reduce context switching

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 a single channel for requests to the Kitfox team.
  3. Regular education sessions 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 on how to find debug info with the help of CloudWatch
  6. Be ready to support new functionality beforehand with information from SAs, and TLs.
  7. Engage teams to create Jira with full description
  8. Proper log aggregation to ElasticSearch and Kibana 
  9. Smoke tests suite for env validation after provision (5 mins) - collab with AQA team needed
  10. Make this process of reviewing possible solutions ongoing.

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.