TAS'mania! Successes (and failures) at TSA Agile Services

TSA Agile Services (TAS) began on January 4th, 2017 after extensive collaboration with contracting officials, various bids, and the Agile community. Come hear the aspects that have enabled successful delivery within a government agency. Also - because transparency is a large key to our success - we will cover the failures we have experienced and the struggles we are still working on. Lastly - it is important for contractors and government to work closely together - this presentation will be co-presented by two Agile Coaches: one is a federal employee and the other a contractor.

 
6 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  1. Intro
    1. I'm a mac, I'm a PC - what we each contribute today
    2. Dave's background before TAS
    3. Yogita's Background before TAS
    4. the 2 foot rule
  2. Structure - just 'safe' enough
    1. I'm a mac, I'm a PC - who we each support
    2. types of teams on TAS
    3. types of teams supporting TAS
  3. The players
    1. I'm a mac, I'm a PC - what we do at work
    2. GPM role on TAS
    3. PO role on TAS
  4. Lots and lots of meetings
    1. I'm a mac, I'm a PC - when we facilitate, when we 'show up'
    2. Sprint Reviews
    3. SoS... wasn't always with 'chickens'
  5. Getting better all the time
    1. I'm a mac, I'm a PC - we identify problems together
    2. Increasing CRM support to TAS
    3. classroom training
    4. in a meeting training

Learning Outcome

  • appreciation of what worked at TAS
  • understanding of why TAS is successful
  • understanding of how to repeat TAS success

Target Audience

Agile enthusiasts with experience and interest in Agile in Government - especially Government Product Owners and Managers;

Prerequisite

Appreciation for dealing with Agile on an enterprise level.

schedule Submitted 2 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  1 month ago
    reply Reply

    David, Yogita,

    This is intriguing, but I'm left wondering what sort of successes? And more importantly, what sort of failures? When I read the outline, I don't get a sense of anything that will fulfill the promise of the title.

     - George

    • David Fogel
      By David Fogel  ~  3 weeks ago
      reply Reply

      GOOD NEWS!  the topics covered have been approved by TSA.  I've attached our first draft of a slide deck - which lists some of the failures and successes we are prepared to share.  

      Yogita and I plan to reorganize the slides (and the outline) into somewhat different buckets.  Also, we will be adding some quotes and images to illustrate how TAS tries to be Agile and Lean.

    • David Fogel
      By David Fogel  ~  1 month ago
      reply Reply

      George,

      I hear you and appreciate the feedback.  Since we are representing the TSA, there are tiers of approval we are working on.  We plan to update the outline - and add slides in the next couple weeks.

      -Dave


  • 45 mins
    Workshop
    Intermediate

    Imagine you were hired to provide consulting assistance for a new team just starting out with Kanban. The team has been struggling with their implementation and is looking forward to your expert guidance, support, and advice. It’s your first day and you just walked into the team room to look at their board. You want to make smart observations and thoughtful interpretations so you can have meaningful conversations with the team members. The team starts assembling in the team room for the daily standup and you plan on making some comments afterwards.

    What comments would you make? What thoughtful questions would you ask?

    This interactive presentation provides a detailed look at how to interpret and thoughtfully observe Kanban Boards to better understand the work of your teams. We will start with an overview of the Lean Kanban Method and then proceed through a series of interactive exercises that give you an opportunity to review and interpret various Kanban boards. The exercises will increase your understanding of Kanban systems and provide opportunities to practice interpreting various board setups so you can have thoughtful and meaningful conversations with your teams.

  • Jim Damato
    Jim Damato
    Transformation Advisor
    Scrum Inc
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Change is hard (duh!) but the book Switch changed my life. While there are lots of change management models out there, Directing the Rider, Motivating the Elephant and Shaping the Path is the one I follow.
     
    Scaling is hard too. But if we think about Change and Scaling together in the right way, maybe they don’t have to be quite so hard.
     
    Recent polling of thousands of Scrum practitioners in the U.S. and Europe indicate that 66% of organizations are at the beginning stage of scaling Scrum. The State of Scrum report says 52% say their "organizational design and culture made it difficult to adopt and further scale Scrum". The State of Agile report says 63% say their "Company philosophy or culture [are] at odds with core agile values"
     
    Think about your organization. Are executives disengaged? Are the agile teams executing independently like feral cats?
     
    Come and learn three actionable things to make your scaling more successful, three things you can implement tomorrow to Direct the Rider, Motivate the Elephant and Shape the Path.

  • Liked Daniel Davis
    keyboard_arrow_down

    Daniel Davis - So You Want To Go Faster?

    45 mins
    Talk
    Beginner

    How frequently does a good agile team deploy to production? Not every team is capable of deploying "on every commit". What does it take for a team to even start deploying at the end of each sprint, or each week, or each day?

    Most companies don't realize that deploying more frequently often requires both significant technical change as well as cultural change. In this talk, I'll guide you through what it takes to deploy more frequently, both from the technical side of setting up pipelines as well as the organizational side of removing red tape. I'll draw on the unique challenges that teams must overcome at each step of the way, from deploying once a month all the way down to full continuous delivery. If your team has been struggling to go faster, come see how you can change to get there. And if you already are at full continuous delivery, come see how to go even faster than that!

  • Liked Raj Indugula
    keyboard_arrow_down

    Raj Indugula - Teams that Plan Together, Plan Better: Big Room Planning in the Enterprise

    Raj Indugula
    Raj Indugula
    VP, Technology
    LitheSpeed
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Any kind of planning is an exercise in uncertainty.  Especially so in large enterprises where delivering value to the customer involves multiple teams within and across organizational silos. Although made popular by SAFe’s PI planning event, Big Room Planning has been used successfully by many organizations to connect the work of their agile teams to the overarching business strategy and to what they can deliver.  

    In this session, we will share our recent story on how Big Room Planning ideas were used in a large Fortune 100 company to align teams, stakeholders, leadership on desired business capabilities, surface uncertainties, dependencies, and reach shared understanding and consensus on achievable outcomes in the near-term.

    It is our hope that some of the ideas discussed and resources shared in this session will help you and your teams with your near-term planning horizons, especially those attempting to drive agility in large, complex organizations.

  • Liked Joshua Seckel
    keyboard_arrow_down

    Joshua Seckel - Lean Large and Small

    Joshua Seckel
    Joshua Seckel
    Chief Engineer
    WhiteHawk CEC
    schedule 2 months ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Most organizations are embracing the desire to be lean, at least espousing the desire.  But what does lean mean in different contexts? Is embracing lean as a startup different than lean delivery as a midsize company or a large organization or a government agency? 

    This talk will explore what it means to be lean in various sized organizations, what is the same and what is different about lean implementations based on the size of the organization.

  • Liked PHILLIP MANKETO
    keyboard_arrow_down

    PHILLIP MANKETO - Building Strong Foundations…. Underwriting Fannie Mae’s Agile Transformation

    45 mins
    Experience Report
    Advanced

    Over the course of the last two and one-half years, Fannie Mae has worked aggressively to transform itself from a heavily silo’d and firmly entrenched command and control culture, following a gated workflow, with long release cycles, to an Agile organization.  Today, Fannie Mae is a more dynamic value oriented organization that is responsive to stakeholders, focused on achieving greater efficiency by enabling fast-feedback loops, as well as using empirical data to optimize mature and persistent agile values and practices.  

     

    Within the larger context of the transformation to enterprise agility, this Experience Report will focus on the case for change, Fannie Mae’s journey and the corresponding challenges, benefits and key learnings realized.  Our conclusion, while it is important to build bridges with business stakeholders, mature agile teams, leverage automation and embrace the values and principles of the agile manifesto… a successful and longstanding transformation is dependent upon the unrelenting focus on changing the ecosystem supporting the organization’s change at the outset.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Creative Solutions to Already Solved Problems

    10 mins
    Experience Report
    Beginner

    Almost everyone has to deal with bad legacy code at some point. Not just legacy code that you inherited and obviously would have been better if you had written it, but legacy code so ugly and ill-conceived that it makes you want to hunt down the person responsible just so you can scream at them (or worse). And then replace it with a one-line library function that does the same thing.

    We'll show some examples of the worst code I've seen, and we'll have a chuckle or a groan. The names, projects, and check-in comments have been changed to protect the guilty, but, unfortunately, these examples are all too real.

  • Liked Jonathan Kauffman
    keyboard_arrow_down

    Jonathan Kauffman - Current State of BDD Testing Tools

    Jonathan Kauffman
    Jonathan Kauffman
    Consultant
    Coveros, Inc.
    schedule 5 days ago
    Sold Out!
    10 mins
    Talk
    Beginner

    Have you heard about BDD and want to start using it, but don't know what BDD is and which tool you should use? In this presentation I address both of those concerns -- I start by providing an overview of BDD and then compare five tools that can be used for BDD testing. I conclude by discussing the pros/cons and popularity of these tools so that you can make an informed decision as to which tool would work best within your organization.

  • Liked Glenn Buckholz
    keyboard_arrow_down

    Glenn Buckholz - Improving Your Testing Methodology Using Docker

    Glenn Buckholz
    Glenn Buckholz
    Technical Manager
    Coveros
    schedule 1 week ago
    Sold Out!
    45 mins
    Tutorial
    Beginner

    Wonder how you can make your testing more efficient? Join Glenn Buckholz as he explores Docker, a technology that allows rapid development and deployment via containers. First, he explains exactly what composes a container, and discusses the differences between a container and an image. Once this is clear, Glenn demonstrates how Docker solves the problem of what he calls the state capture problem. When a test case produces a failure, the developer and testers often expend significant effort reproducing the issue so the developer can see the issue and fix it. Glenn demonstrates how Docker enables succinct, accurate, and quick communication between testers and developers, helping mitigate the state capture problem. In addition, testers can use Docker to load data, efficiently insert testing tools into a running system, set system state, and aid in test reproducibility. After you look at the inner workings of Docker and run through a few practical examples, you’ll find that Docker will hold an important place in your testing toolbox.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Experiences Bringing Continuous Delivery to a DoD Project

    Gene Gotimer
    Gene Gotimer
    Technical Manager
    Coveros, Inc.
    schedule 3 weeks ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Not every continuous delivery initiative starts with someone saying "drop everything. Let's do DevOps." Sometimes you have grow your practice incrementally. And sometimes, you don’t set out to grow a practice at all-- you are just fixing problems with your process, trying to make things better.

    I'll walk through a case study of how our team worked on an exemplar project for the Department of Defense to show that agile could work in a decidedly waterfall culture. I’ll also discuss techniques and tools we used to bring a DevOps mindset and continuous delivery practices into an environment that wasn't already Agile.

    I'll talk about how we were able to start in development, where we had the most control, with a "let's starting being Agile" initiative and working on "why is continuous integration important?" From there, we tackled one problem after another, each time making the release a little easier and a little less risky. We incrementally brought our practices through other environments until the project was confidently delivering working, QA-tested, security-tested releases that were ready for production every two weeks. I’ll discuss the journey we took and the tools we used to get to build quality into our product, our releases, and our release process.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Tests Your Pipeline Might be Missing

    Gene Gotimer
    Gene Gotimer
    Technical Manager
    Coveros, Inc.
    schedule 3 weeks ago
    Sold Out!
    10 mins
    Talk
    Beginner

    Developing a delivery pipeline means more than just adding automated deploys to the development cycle. To be successful, tests of all types must be incorporated throughout the process in order to be sure that problems aren’t slipping through. Most pipelines include unit tests, functional tests, and acceptance tests, but those aren’t always enough. I’ll present some types of testing you might not have considered, or at least might not have considered the importance of. Some types will address code quality, others code security, and some the health and security of the pipeline itself.

    I’ll talk about specific tools we used to supplement our pipeline testing. I won’t get into how to use each tool-- this is more of a series of teasers to encourage people to look into the tools, and even letting them know what types of tools and testing opportunities are out there.

  • Liked Gene Gotimer
    keyboard_arrow_down

    Gene Gotimer - Which Development Metrics Should I Watch?

    Gene Gotimer
    Gene Gotimer
    Technical Manager
    Coveros, Inc.
    schedule 3 weeks ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    W. Edwards Deming noted that “people with targets and jobs dependent upon meeting them will probably meet the targets – even if they have to destroy the enterprise to do it.” While metrics can be a great tool for evaluating performance and software quality, becoming beholden to reaching metrics goals, especially the wrong ones, can be detrimental to the project. Each team needs to take care and understand what targets are appropriate for their project. They also need to consider the current and desired states of the source code and product and the capabilities and constraints of the team.

    As one of the lead architects working with a huge codebase on a government project, I often have the opportunity to influence the teams around me into watching or ignoring various metrics. I will walk through some measures that are available to most projects and discuss what they really mean, various misconceptions about their meaning, the tools that can be used to collect them, and how you can use them to help your team. I’ll discuss experiences and lessons learned (often the hard way) about using the wrong metrics and the damage they can do.

  • Liked Colleen Johnson
    keyboard_arrow_down

    Colleen Johnson - End to End Kanban for the Whole Organization

    45 mins
    Talk
    Intermediate
    We often look to our engineering teams first to drive efficiency and speed to deliver but as we optimize the flow of our development processes we quickly create pressure in the organizational workflow with the activities that feed into and out of product delivery.  Product definition struggles to keep pace and establish a queue of viable options to pull from.  Marketing efforts begin to pile up as features release faster than we can share the news.  All of this stems from optimizing only one part of the overall system.  In this talk we will look at how to scale Kanban practices to the entire organization to provide the visibility, flexibility and predictability to make every part of the business truly agile.  
  • Liked Rahul Sharma
    keyboard_arrow_down

    Rahul Sharma - Building and Testing Secure Mobile Applications

    Rahul Sharma
    Rahul Sharma
    IT Consultant
    Coveros
    schedule 4 days ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    Mobile application development has been on the rise lately because of the convenience mobile apps have to offer. Despite the recent occurrence of security breaches on mobile devices, security testing is not as emphasized as other forms of testing such as user acceptance or functional testing. An application can consist of the greatest features but will be considered unusable if hackers can exploit it. The exponential rise in the use of mobile applications for different purposes puts mobile devices in significant danger of being hacked or compromised. In today’s world, mobile applications are used for various purposes and store Personally Identifiable Information (PII) and financial information. Due to the sensitivity of customer data, mobile applications should be built and tested with security in mind. Strategies that cover how to properly test mobile apps for security issues will be discussed.

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - How do I know if I have the right Product Owner?

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 5 days ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Is your Product Owner available to the team, empowered to make decisions, knowledgeable in their business domain, engaged in the product and leading the way for delivery of value? This session does a deep dive in the these ideas.
The session starts with a brief Seinfeld video to demonstrate the importance of Product Ownership. The session then discusses 5 key attributes to look for in a Product Owner:

    1. Bandwidth
    2. Power

    3. Knowledge
    4. Interest
    5. Vision

    After that discussion, we will have an interactive exercise to identify what a Product Owner does day to day. The debrief will identify the balance a Product Owner must have between working with stakeholders, end users, customers AND working with the Scrum team AND product backlog refinement.

    The session concludes with the presenter sharing a Product Owner persona sheet. This persona sheet measures product owners across the 5 attributes mentioned above and presents a narrative on their core strengths and risks.

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - Group Hug: Implementing Agile Across Multiple Teams

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 5 days ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The patterns for implementing Scrum at the team levels have largely been set, but what about dealing with Agile and Scrum across multiple teams. Is the answer just magical words like scaling, or SAFe, or LeSS? What are the core concepts and successful patterns? Is it just one big group hug?

    In this session, we will explore core concepts around implementing Agile concepts across multiple teams. The session starts with a simulation that explores distributing people across teams (which will actually NOT involve any hugging). From there, this session dives into:

    • Prioritization across multiple teams
    • Product Ownership across multiple teams
    • Dependencies and team alignment
    • Communities of Practice
    • Communication and collaboration across teams
    • The role of managers
    • A quick look at scaling methods

    Coming out of this session, attendees will have an understanding of core concepts and fundamental helpful practices in implementing Agile concepts across multiple teams.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Let's Sharpen Your Agile Ax ... It's Story Splitting Time

    Brian Sjoberg
    Brian Sjoberg
    Agile Coach
    Excella Consulting
    schedule 1 week ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Do you want to write great User Stories (a.k.a. small features that are part of a product) that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with completing stories (of business value) that are potentially shippable within a fraction of an iteration/sprint? During this session we will do a quick refresher on User Story formatting to include Acceptance Criteria. The reason for the refresher is that over the last few years, despite people using User Stories, I have experienced their usage far from the intended purpose.

    After the refresher, we will learn at least 2 techniques for splitting stories in this interactive workshop.

  • Liked Thomas Stiehm
    keyboard_arrow_down

    Thomas Stiehm - Agile Testing for Embedded Software Development

    Thomas Stiehm
    Thomas Stiehm
    CTO
    Coveros, Inc.
    schedule 1 week ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    A large part of the success of agile adoptions is due to the automated testing approach used in agile projects. Because many of these techniques were pioneered in the development of web applications it can be hard to see how these techniques can be leveraged for a project where the software being built is for an embedded application. Discover ways to leverage agile testing techniques for embedded systems. Whether you are building a medical device, embedded controller, or Internet of Things device learn how to leverage these testing practices to create fully automated tests that fit into a DevOps build pipeline and help your team create higher quality, more reliable software. Test automation is the best way to maintain and execute a comprehensive suite of regression tests that allows you to take back control of your testing process while increasing test coverage. Learn how to be in control of your test process by stepping up your test automation to the next level.

    Embedded development and Internet of Things development is often done on platforms that lack modern software development and test automation tools. The more esoteric or the smaller the target audience, the less likely tool vendors are to create products that directly support the deployment environment. This can make getting started with test automation using older tools that are not as actively supported by vendors can be a challenge that has to be overcome by a team that wants to move toward a Continuous Deployment process.

    This session is aimed at people that are trying to adopt agile and continuous delivery with embedded technology, but might be worried that it can’t work in their particular environment due to their industry, technology stack, culture, or regulatory environment.

  • Liked Julie Wyman
    keyboard_arrow_down

    Julie Wyman - Managing Resistance: How the Kanban Method Supports Lasting Change

    45 mins
    Talk
    Beginner

    “Going Agile” is a big cultural change for most organizations and it’s significance, impact, and the effort required for successful implementation can often be underestimated. There are many benefits to be gained by adopting a more Agile approach, including quicker feedback loops, more focus on value, and higher levels of collaboration. However, for Agile to succeed in the long-term it’s essential to set expectations up front and to balance the amount of change with the amount of disruption it will cause. In this session, we will look at how David Anderson intentionally built change management principles into his Kanban Methodology and explore other change management techniques the Agile community can leverage when helping organizations transition to Agile.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Understanding the Whole System, Not Just a Part

    45 mins
    Tutorial
    Beginner

    Are your solutions to recurring issues having only minor improvements? Are some of these solutions actually making things worse in the long run? When answering yes to these, typically, we are trying to solve the issues with too narrow a view. Oddly we think we are addressing it at sufficient level but usually not. In order to see the entire picture we need a common language that will enable us to understand an entire complex adaptive system (e.g. organizations, teams, individuals). Join us as we learn a language called System Modeling (aka. Causal Loop Diagrams).

    With this language we will be able to have rich dialogue to gain a full understanding of the entire complex adaptive system so that we can create solutions at the fundamental level and not the symptomatic level. Addressing system issues at the fundamental level will significantly improve the system. Symptomatic solutions may give the appearance of improvement in the short term but typically make things worse in the long run. Unfortunately we usually pick the symptomatic solutions because they seem obvious and we don't realize the long term impacts because of feedback delays that could take weeks, months or even years to realize.