At the Crossroads of Agile and Automation - AWS MENA

At the Crossroads of Agile and Automation - AWS MENA By Joe Scholz

Transcript

1. COMMUNITY DAY MENA At the Crossroads of Agile and Automation
2. Introductions 2 Joseph Scholz Agile Delivery Lead Joe’s professional journey has been eclectic. He started as a Teacher and then moved to playing basketball in Spain. After that he worked at a Cafe and eventually settled in IT as an Agile Delivery Lead for the past 4 years. Currently he works with Cloud Engineering Teams to improve processes and delivery Enterprise solutions
3. Introductions 3 Eric Schultz Senior Software Engineer Eric is a Senior Software Engineer at Capital One. His role is focused on cloud engineering and compliance while improving the developer experience. Eric has experience with several cloud platforms and managing enterprise workloads.
4. Agenda 4 • Background • Agile Intent • Crossroads Solution
5. Background 5
6. Compliance Opportunities 6 • Limit the amount of compliance notifications (email overload)
7. ‘Radio Noise’ Effect 7
8. Compliance Opportunities 8 • Limit the amount of compliance notifications (email overload) • Track and Prioritize efforts with Agile principles • Automated validation instead of verifying manually
9. What We Built 9 • Integrated Solution that leverages Agile principles and single source-of-truth verification • Automated workflow to map work items to Cloud resources
10. Agile Intent 10
11. Basic Agile and Business Intent • Provide a consistent and organized format • Adhere to established Agile patterns • Give contextual information • Control over the creation of work • Tracking and Metrics 11
12. Agile Nomenclature and Hierarchy • ‘Issue’ is a generic term for any work item. It doesn’t mean ‘bug’ or ‘defect’ even though it sounds that way, so we will try not to use that term • ‘Epic’ is a defined effort with a result (e.g. Amazon Machine Image Rehydration ‘Epic’) • ‘Story’ is a unit or part of an Epic such that all Stories must be complete for the overall Epic to be done (e.g. AMI Rehydration for a specific cloud resource) 12
13. Consistent Format 13
14. Visualize the Work and Involve the Team 14
15. Provide Criteria and Prioritization 15
16. Single Source of Truth • Dedicated Agile ‘parent project’ 16 • System Account with project access ◦ reduce the noise • Labels and Custom Fields ◦ Sorting ◦ Queries
17. Produce Metrics for Accountability 17
18. Crossroads Solution 18
19. Initial Implementation • Architecture ◦ Python package ◦ Batch (AWS Lambda) ◦ DynamoDB (NoSQL) • Dependencies ◦ jira-python ◦ Jira API ◦ Boto3 ◦ ServiceNow API 19
20. Discovery Clients • Discover non-compliant AWS resources ◦ Across several AWS Accounts • Discovery Client per AWS resource type ◦ Example: S3 • Return value ◦ non-compliant resources grouped by Team - “Team” Tag 20
21. Jira Creator Client • Input ◦ Cloud control / Epic ◦ Discovery Client output • Stories are created per team • Creates / Updates / Closes Stories ◦ Create - no story exists or story is closed ◦ Update - story exists and story is open ◦ Close - story is open • DynamoDB 21
22. The Life of a Story - Daily Cycle 1.Creation a.Boto3 i. Gather resources ii. Sort by Team iii.Create Story per Team Description includes list of resources 22
23. The Life of a Story - Accountability 2. Assignment a.Service Now i. Engineering Lead b.Additional Stakeholders i. Product Owner ii. Agile Delivery Lead 23
24. The Life of a Work Item - Compliance Assignment 3. Epic a.1 Epic per Cloud Control b.1 story per team c. Each story is assigned to the epic d.Track company’s overall completion status 24
25. The Life of a Story - Team Management 4. Workflow Progression a.Team can make manual transitions Backlog -> In-Progress 25
26. The Life of a Story - Automated Workflow 5. Closing a.Validation i. Resources’ action items are completed b.Completion i. Closed Status ii. Comment 26
27. Workflow • Daily Trigger • Multithreaded ◦ 1 per Cloud Control • Discovers resources • Jira Actions ◦ Create/Update/Close • Stores results in DB 27
28. Results 28
29. Results • Clear Expectations for the Teams • Iteration and Roadmap Planning Capability • Accountability and Actionability • Ability to evaluate team efforts for improvement • Easier tracking through a defined system of record • Peace of mind 29
30. Questions and Conversations 30
31. That’s All Folks 31 Contact Joseph.Scholz@capitalone.com Eric.Schultz@capitalone.com Facebook – Agile Joe Instagram @AgileCupOfJoe LinkedIn - ericschultzd