How I Went Through Basic Military Training with Basic Agile Principles

As a 33 year old I decided it was time to follow my life-long dream of serving my country as a member of the United States Air Force. I went to Basic Military Training (Boot Camp) thinking that I could use all of my Agile experience to make things easy...it was far from easy. However, I was able to incorporate Agile Principles along the way to help our diverse group of over 45 trainees succeed, and I learned some good lessons to take back to my Agile Teams as well. I am excited to share my experience with all of you.

 
 

Outline/Structure of the Experience Report

Introduction

Using Agile in Basic Military Training

Influence of Basic Military Training on my Agile Teams

Conclusion and Discussion

Learning Outcome

The importance of Agile Fundamentals

How to perform as an Agile Team

Target Audience

Team members using Scrum of Kanban who want to refocus their Teams on Agile fundamentals

Prerequisites for Attendees

No prerequisites other than be willing to have fun.

schedule Submitted 2 years ago

  • Colleen Johnson
    Colleen Johnson
    ScatterSpoke
    schedule 2 years ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Change is inevitable. In this talk we will discuss the four facets of change that are constantly affecting us: changing products, changing priorities, changing people and changing process. We will look at where these changes comes from, the impacts they have on us and explore concrete tools we can use to get better at responding to them. Attendees of this session will leave with a new attitude on the churn that takes place around us everyday. They will learn to acknowledge the benefits that changes have so they can truly welcome it into their team, their practices, and their life.

  • Trent Hone
    Trent Hone
    Excella
    schedule 2 years ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Customers weren’t satisfied! The process took too long! The end product didn’t perform to specifications! Does this sound familiar?

    A century ago, the U.S. Navy’s ship design process had serious problems, ones we would recognize and understand today. Come learn how these problems were solved in a large, real-world, organization through minor changes in structure and process. These changes illustrate the importance of:

    • Gathering early feedback
    • Rapidly iterating to expose unknowns
    • Using multi-disciplinary problem-solving
    • Employing Agile techniques outside of IT
  • Victoria Guido
    keyboard_arrow_down

    Victoria Guido - Avoiding Pitfalls of Non-Technical Managers

    10 Mins
    Lightning Talk
    Beginner

    This talk is intended to help folks who are managing technical projects avoid common pitfalls, and help technical teams better prepare managers for overall project success.

  • Lizzie Berkovitz
    keyboard_arrow_down

    Lizzie Berkovitz / Khadijah Anderson - Using Agile to Boost Diversity, Inclusion, Creativity, and Employee Satisfaction

    45 Mins
    Case Study
    Intermediate

    In a diverse company full of schedule-packed consultants and engineers, how do you continually find ways to engage employees and create a more inclusive environment? Khadijah and Lizzie knew they had the support of leadership – and the interest of the employees – so all they had to do was come up with a way to learn quickly, fail fast, and prototype.

    Come hear how Lizzie and Khadijah, along with their fellow Blackstonians, applied Agile Principles to solve a decidedly non-IT challenge.

  • JeffreyMFarley
    keyboard_arrow_down

    JeffreyMFarley - What Works - Project Transitions

    JeffreyMFarley
    JeffreyMFarley
    Solution Architect
    STSI Inc.
    schedule 2 years ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    Most days on a project are the same. Team members are incrementally improving the application, fixing bugs or adding features.

    But what about those “special days”?

    • The project is started
    • A new person joins the team
    • The team goes remote
    • A team member moves on
    • The project launches to a wider audience

    There is a lot of digital ink spilled about the right way to run a project day-to-day, but I will focus on what has worked for me on each of those “special days”

  • Ben Morris
    keyboard_arrow_down

    Ben Morris - Agile the Hard Way - Lessons from a Government Project

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 2 years ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    Most government agencies are becoming 'agile'. A few are actually diving in to focus on frequent delivery of software that creates business value. This is not about 'agile' the easy way - implementing a few ceremonies, titles, and buying a software package, then declaring victory. This is about agile the hard way - the stubbed toes and small victories that open the door to lasting change.

    The talk walks through lessons learned from a specific government project, jumping head-first into agile, open source, and (oh dear) the cloud.

  • Alex Martins
    keyboard_arrow_down

    Alex Martins - Continuous Testing to Truly Achieve In-Sprint Test Automation

    45 Mins
    Case Study
    Beginner

    You say your team has adopted agile development practices and that may be true. But, what about your testing? How agile is that? Are you stuck in manual testing mode? Oh, you do automate tests, but it’s never In-Sprint? And you just run automated regression tests within the Sprint? So… the tests you automate are regression tests, not tests validating stories being delivered in the current sprint, right? And you have a separate test automation team that can never keep up with maintenance and is always lagging behind? What about test data? And interfacing systems to your application that are never available? Head exploded yet?

    If any of this sounds too familiar, it’s time for a new approach to speed up testing and become truly agile, across the board: Continuous Testing.

    We'll go over some proven Continuous Testing practices that helped us truly achieve Nirvana around testing in an Agile team, such as:

    • Shift testing all the way to the left - starting with your backlog grooming sessions
    • Automatically generate test automation scripts... that's different then run them in an automated fashion
    • Achieve maximum coverage with the smallest set of test cases. For a fact.
    • Fully integrate testing into the application pipeline.
  • Ben Morris
    keyboard_arrow_down

    Ben Morris - Stop being so excited about agile.

    Ben Morris
    Ben Morris
    Consultant
    STSI
    schedule 2 years ago
    Sold Out!
    10 Mins
    Lightning Talk
    Advanced

    Many professionals get excited about agile. I don't get excited about agile, and I'd argue that you shouldn't either. This agile-first mindset is counterproductive and dilutes the quality of discussion about our craft.

    What I get excited about is building great software. Agile literature provides a useful toolbox that can help us do that better.

    Listen to me wax curmudgeon for a few minutes, then invite counter-points from the audience. Change my mind - I no doubt lack some context or experience. My opening salvos to spur debate include:

    • Agile shouldn't be applied to non-software projects.
    • Agile coaching is overrated.
    • Projects or job titles should not include the term "agile".
    • Don't put certifications in your e-mail signature.
  • JeffreyMFarley
    keyboard_arrow_down

    JeffreyMFarley - Agile Comics

    JeffreyMFarley
    JeffreyMFarley
    Solution Architect
    STSI Inc.
    schedule 2 years ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    My first comic took one year to produce, my second took one month. What changed?

  • Robin Yeman
    keyboard_arrow_down

    Robin Yeman / Dr. Suzette Johnson - Industrial DevOps

    45 Mins
    Talk
    Intermediate

    Industry lead and cycle times for delivering significant cyber-physical solutions—systems such as robotics, warfighting, transportation, complex medical devices, and more—are insufficient to meet the increasing demands of our customers. As the size and complexity of cyber-physical systems increase, the visibility of the work items and activities in the value stream decrease, compounding the problem. Additionally, many large-solution providers are organized around functional areas and apply traditional, sequential, stage-gated development methods, resulting in multiple handoffs and delays. The net result is usually slow time to market, quality issues, cost overruns, and solutions that are not fit for their intended purpose.

    Robin Yeman and Suzette Johnson both work for large government contractors where it has been imperative to scale DevOps and to optimize practices for delivery across software, firmware, and hardware. They will discuss best practices obtained from lessons learned across many complex systems.