Testing sprints? Hardening sprints? Why do so many of us have these and other ways to get around completing all our required testing inside our defined timeboxes? Isn’t our goal to produce deployable features at the end of every Sprint?

During our session, we will examine why it’s so hard to accomplish all necessary testing inside the iteration and show how to complete these tests within your timebox. Through interactive discussion and real world examples, we will provide insights on foreseeing, overcoming, and avoiding your hurdles and send you home with both long term methods and short term actions that will yield tangible results in achieving your goal.

Our session will:
• Illustrate the value of completing all of your testing inside your timebox
• Identify the challenges in completing all these tests in such as seemingly short period of time
• Discuss ideas and options to successfully overcome these challenges
• Explore how to enable your organization and environment for efficient, rapid testing
• Discuss real world examples of enablement and how we navigated the pain points of enabling testing processes that allow complete testing within an iteration
• Explore DevOpsSec and how achieving testing within your timebox is a precursor to DevOpsSec
• Provide short term tactics and actions to immediately improve your ability to complete your testing
• Allow you to voice your concerns and challenges and discuss potential solutions to these impediments

Most of us implement agile to reduce the time to deliver valuable working software and to increase the frequency of delivery with high quality through increased and earlier collaboration, shorter feedback loops, and reduced risk. While you can show improvement over Waterfall by performing typical agile methods, you cannot really live the dream without optimizing your agile execution.

You will leave this session armed with the right knowledge to improve delivery on your current project or start your new projects properly so that you or your clients can reap the benefits of efficient process and high-quality software capable of achieving continuous deployment of fully-tested code at the end of each iteration.

 
4 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

We will lead discussion and facilitate a number of activities addressing questions such as the necessary skills to deliver quality, how to complete an extensive number of tests in such a limited amount of time, the role of the “testers” on the agile team, how to perform compliance tests and non-functional tests within the iteration window, and how to move toward continuous testing, continuous integration, continuous deployment, and strive for DevOpSec execution where all necessary parties are involved and collaborating from the beginning of the effort to ensure effective delivery. We will illustrate these areas using real world examples from projects we have delivered.

Session Agenda:

•(5 Mins) Introduce speakers, state our goal, define Testing Within Your Timebox, poll attendees, illustrate why it is important to Test Within Your Timebox
•(5 Mins) Activity: Produce a list of challenges the participants have faced, or believe they will have, trying to complete all testing inside their Sprints
•(5 mins) Describe the challenges which we have experienced
•(7 Mins) Activity: Ask the attendees to participate in solutioning the list of audience challenges
•(10 Mins) Present additional solutions we have considered, Testing Continuum, and Overview of an Optimized Solution
•(12 Mins) Practical application: A Day in the Life, Enabling Platform, and How Testing Inside Your Timebox is a precursor to DevOpsSec
•(3 Mins) Provide immediate takeaways that participants can use the next day
•(13 Mins) Questions and Answers

We will cite specific examples about challenges and successes from our client experiences. We plan to use several examples from our clients (USDA, ICE, DHS HQ, ESDO, and USCIS).

Learning Outcome

Session Goal: Provide attendees with the knowledge necessary to understand what it is to Test Within Your Timebox, why they would want to do it, what challenges lie ahead, and how to overcome/avoid them. Provide takeaways for immediate benefit they can use on their current projects.

Through this session we intend for you to leave with the following knowledge:

  • What it is to test within your timebox
  • To understand what the complete set of tests are that ought to be performed, especially in Federal programs and/or those with elevated regulations
  • The benefits to performing all testing within your sprint
  • Understanding the pitfalls and challenges
  • Knowing how to overcome the pitfalls and challenges and the solutions that avoid/address these
  • To understand what an ideal solution would include
  • An introduction to a fully-automated enablement stack to ensure success in completing your testing within your timebox.

Target Audience

Anyone on an agile project team as well as their executive leadership and client leadership

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Shawn Faunce
    keyboard_arrow_down

    Shawn Faunce - Engaging a Product Owner on a Government Contract: Challenges and Solutions

    30 mins
    Talk
    Beginner

    Great systems require active, capable Product Owners.  Functional innovation is not possible without their commitment and involvement in the project.  Too often in government contracting, the Product Owner is an Absentee Owner.  Agile Development teams often seek out tools and techniques to create great systems, however too frequently what is holding them back is the lack of an engaged Product Owner. Teams in this situation must face the elephant in the room if they desire to build a system that brings positive change in efficiency, productivity, quality, usefulness, and adoption.  This talk shares solutions I have used for challenges I see again and again on government contracts.

    The talk begins with some introductory material on the problem, its causes, what I mean by functional innovation, and why this is required to build great systems.  I describe four challenges with Product Owner engagement that are not unique to government contracting, but that I see recurring on projects: committing staff, procurement practices, role ambiguity, and absentee ownership.

  • Liked Dan Neumann
    keyboard_arrow_down

    Dan Neumann - Principle-Centered Agility: Your Path to Better Options

    Dan Neumann
    Dan Neumann
    Agile Coach
    AgileThought
    schedule 3 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Do you want to have a high functioning Agile team? If so, this session is for you! We're going beyond the rules of agile frameworks and learning to apply those principles to improve our teams and companies! The 12 principles of the Agile Manifesto capture the reasons we are able to deliver better software. This is the "why" for some of the rules behind Scrum and Kanban. The principles ought guide our decisions about practices, scaling, and solving tricky problems!

    In this session, we will use the 12 Principles of the Agile Manifesto as our foundation. Then, we will  apply techniques such as Force Field Analysis to apply the principles to your challenges at work. Lastly, we will use principles of change management to make the change more likely to stick.

    The outline for the session is:

    1. Explore the principles; which ones are present or absent in your environment?
    2. Introduce Force Field Analysis
    3. Use Force Field Analysis to explore what drives a specific behavior
    4. Use the Agile Principles to generate new options for tackling your team's challenges
    5. Explore effective change management techniques

    With these five activities, you will leave with a framework for change to apply when you return to work and continue on your agile journey.

  • Liked Darren Hoevel
    keyboard_arrow_down

    Darren Hoevel - Kicking off an Agile Product, Team and Culture

    Darren Hoevel
    Darren Hoevel
    Agile Coach
    Pliant Solutions
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    As Agile sweeps through the industry at amazing speed, organization struggle how to “transform” their culture and adapt their project execution in their new enterprise. Meanwhile, the business and IT struggle to understand what is expected from them as they enter new projects under the “Agile template”... In this session we will discuss how “setting the stage” for an Agile product, team and organization will help to level set expectations and increase the probability of business value delivery by everyone involved. We will leverage standard project documentation, Agile best practices and facilitation games to emulate a Agile product kick off. Our goal for this session will be to provide the group with an Agile kick off “template” that will increase team buy in and minimize team hurdles along your journey to happy customers. DISCLAIMER: No magic fairy dust will be provided... just a compilation of tools for you to utilize as you feel fit.

  • Liked Matt Badgley
    keyboard_arrow_down

    Matt Badgley - Yes, Words Really Do Mean Things - Establishing a Shared Language

    60 mins
    Workshop
    Intermediate

    During this conference, within the books we read, in our day-to-day lives -- we use words as a means to negotiate, interact, express, and do. Words, whether written or spoken can play differently based on the people that exchange them. In the world we are living today, words are bantered so freely that they cause a war or unite a community or save a marriage or demoralize a team.

    As we see today, the concepts of agile are permeating the enterprise and scaling out from the team to the program management office to the executing chambers. Words are often mis-used, mis-understood, and lead to bad behaviors.

    In this session, we'll discuss the general challenges of communications and the overwhelming vocalbulary that we have embedded in our craniums.  We'll explore words -- in particular, the words we use everyday around software development. We look at how some of the basic words we use like Velocity, Sprint, and Team have clear meanings and plenty of baggage. 

    To help solidify the learning of this workshop, we'll use a couple brainstorming games -- so come prepared to get engaged. We'll wrap-up by using our collective experiences to either find better ways to explain our words or establish brand new ones. Our ultimate goal is to establish a way an organization can establish an ubiquitous language around the work they do and ultimately improve communication which will lead to better agile transformations and hopefully better solutions.

  • Liked Valerie B Santillo
    keyboard_arrow_down

    Valerie B Santillo - The Role of a Leader in an Agile Organization

    Valerie B Santillo
    Valerie B Santillo
    Agile Coach
    Blue Agility
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    We hear a lot about leaders who don't "get" Agile and the impact they have on Agile adoption but, what is the role of a leader in an Agile Organization? Agile requires a great deal of change in the way we approach, manage and execute delivery. And, while a great deal has been put in place to educate and support team members, Scrum Masters and Product Owners, there isn’t a great deal available to those outside of teams – especially leaders.  This discussion will present a description of an Agile leader for consideration and the results from two organizations:  One who applied the learning, and one who did not.

  • Liked Shannon Ewan
    keyboard_arrow_down

    Shannon Ewan - The Art of Facilitating Agility

    60 mins
    Workshop
    Intermediate

    From an agile implementation perspective, emphasizing the art of facilitation is an incredibly powerful tool for creating a culture of collaboration, and then leveraging that culture as a springboard to organizational transformation.  With strong facilitators at the gateway between business and IT, within IT delivery teams, and at key intersection points within an organization, the challenges to achieving organizational agility diminish. Strong facilitators bring forth the wisdom of teams and provide a container for self-organization. Facilitation is the cornerstone of servant leadership. 

  • Liked Joshua Seckel
    keyboard_arrow_down

    Joshua Seckel - No defects in a government setting? What does that really mean?

    60 mins
    Talk
    Intermediate

    We have heard a lot about no defects or zero defects, but is that reasonable or achievable in the government context?  How else can each sprint be deployable? Or how can you get to true flow with each story deployed to production?

     This session will explore how to get to a no defects posture across all of the tests required in a government setting. 

    We will look at the various types of testing:

    Unit, Functional, Integration, Security, 508, System, User Acceptance, etc 

    We will look at what defects mean and how (or if) they should be tracked

    We will look at what potential impediments from government organziations may exist in reaching a no defect state of software delivery

    We will look at what tools and techniques can be used successfully in the government setting to address the impediments and achieve no defects in released software

  • Liked Roland Cuellar
    keyboard_arrow_down

    Roland Cuellar / Ken - IV&V for Federal Agile Programs: A Customer Experience Report

    60 mins
    Talk
    Intermediate
    1. Many federal government organizations have a requirement to perform independent verification and validation (IV&V) of software development projects for purposes of risk identification and compliance
    2. As more federal agencies move towards agile, they will need to devise agile-appropriate methods for evaulating agile teams and contractors for process performance and project risk identification
    3. Traditional approaches to IV&V are heavily biased towards waterfall, gate reviews, and traditional SDLC artifacts and hence, do not work well within an agile envrionment
    4. Agile programs have their own process-specific risks and issues that need to be evaluated uniquely.  The document-centric approach that has traditionally been used is innapropriate and ineffective for agile teams as it does not find the right risks and does not find them early enough in the development process.
    5. We at DHS/CIS have developed a unique, agile-appropriate IV&V model for a large agile transformation effort within DHS
    6. The model is used to discover process risks, design risks, code risks, and testing risks in real-time for agile teams
    7. The model serves as actionable and real-time feedback to teams, contractors, and federal managers that can be used for process improvement, vendor evaluation, and as a means to find and elevate delivery risks on agile projects
    8. Positive results, challenges, and recommendations related to the development, roll-out, and execution of this agile-appropriate IV&V model will  be shared
  • Liked Alexei Zheglov
    keyboard_arrow_down

    Alexei Zheglov - Five Very Important Numbers And How They Can Help Improve Your Knowledge-Work Organization

    60 mins
    Tutorial
    Intermediate

    This session will be about five numerical characteristics of a process.  (Call them "metrics", but beware we will be discussing only those that are difficult to game.)  I chose five of them that are not often discussed,  rarely measured, and even less frequently used in making decisions.

    This happens partly because of inertia.  In the better-studied world of manufacturing physical products and services, for example, one of these quantities approaches 100%, another one is almost always (ideally) zero, and yet another one is a single number rather than a statistical distribution.  You don't even have to think about them.  But when the customer value is created in the brains of intellectual workers rather than on the assembly line, the five quantities we will be discussing reveal non-trivial insights.

    We will discuss what you can do to measure them when you return to your office on Wednesday.  We will also discuss how you can practially use the new knowledge, starting on Thursday, to find new leverage for improvement, find time for work that is important, but not urgent, balance capabilities of your organization with the demand placed upon it, deal with uncertainty, and forecast the delivery of your projects and other commitments.

     

  • Steve Elliott
    Steve Elliott
    CEO
    AgileCraft
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    We would all agree that Agile is mainstream, agile is the future and that Agile DOES work.  So why then do we see so many failed or moderately successful large scale transformations?  The answer is complex but there are many things that can be done to improve your odds of success.

    In this talk we will explore 7 proven methods to help you see bottlenecks, clear land mines and drive better results.  The seven points we will explore include:

    1. Methods to scale up collaboration (above the team level) using agile principals
    2. New methods to scale up estimation by combining standard methods like WSJF, Points, T-Shirts, Team Weeks with Monte Carlo what-if simulations.
    3. Objectives as work packages
    4. Value streams in a three tier model with a RACI twist
    5. Agile Ghantt-ification and other scaled-up visualizations
    6. The effects of WIP discipline at the portfolio level
    7. How calculate capitalization regardless of team methods (cycle time, points, hours) 
  • Liked Derek Huether
    keyboard_arrow_down

    Derek Huether - At home and work, how to get more stuff done. An introduction to Personal Kanban

    3 mins
    Workshop
    Beginner

    With a world of constant distraction, it feels like it’s getting harder and harder to get stuff done, regardless if it’s on a personal or organizational level. At some point, we’ve been sold the lie that multitasking is great and maximum utilization is even better. If we all agree with that, why are we doing more and getting less done? If there were a relatively simple way for you to get more stuff done, wouldn’t you want to know what it was? If there were a way for you to measure and improve your processes over time, wouldn’t you want to know how to do that as well? When getting stuff done is a primary measure for success, we need to introduce people to concepts that are simple but can be leveraged at scale.

    In this session, participants will be introduced to the principles of Lean and the application of Kanban to visualize their personal work, limit distraction and waste, and get stuff done. I’ll cover the core concepts outlined in Jim Benson and Tonianne DeMaria Barry's book, Personal Kanban, to get you started. I’ll talk about how Kanban can be applied to everyday work and why you should do it. 

    Through my years of struggling with ADD/ADHD and my years of management, leadership, and coaching, I have learned and applied Personal Kanban techniques in my everyday life and Lean Kanban at both government and private organizations. This is your opportunity to learn a few simple strategies that you can start using before you even leave AgileDC. This workshop can help you map your work and navigate your life.

  • Liked bchaplin1
    keyboard_arrow_down

    bchaplin1 - Minimizing Technical Debt Via Agile Metrics and Techniques

    bchaplin1
    bchaplin1
    Metrics Architect
    Chaplin Solutions
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Automate and mine those code quality statistics from Sonar and use Agile techniques to transform your team and codebase!

    Studies show that poor code quality can cut your velocity in half as early as the second release.  But there's hope.  Yes, you can make your deadlines and still have little or no technical debt.  

    Using proper metrics 50% of the 100 committing developers had no tech debt and 100% test coverage for all their code submitted in 2013.  

    Use key code quality metrics to manage your team's quality and ensure your second release is just as productive as the first.    

  • Liked shentonfreude
    keyboard_arrow_down

    shentonfreude / Paul Boos - Making a Better Salad: Behavior-Driven Development with Lettuce

    30 mins
    Tutorial
    Intermediate

    Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format.  This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.

     

    This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce.  You will gain a deeper understanding of how you can apply this to writing your applications.

     

  • Liked Daniel Gullo
    keyboard_arrow_down

    Daniel Gullo - WANTED: Agile Coach, Scrum Master, CEO, whatever... (How to make your Agile transformation successful.)

    60 mins
    Talk
    Intermediate

    The term “coach” has become an overloaded and almost meaningless term in much the same way that “agile” has.  Many individuals are calling themselves coaches who have little or no practical experience with Agile in large enterprise organizations.  Organizations are similarly confused about who they really need to bring success to their Agile transformation, and thus, are advertising for the wrong skills.

  • Liked John Hughes
    keyboard_arrow_down

    John Hughes - Waterfall comfort in an agile world: How to give Execs the answers they "used to get" now that you are agile

    John Hughes
    John Hughes
    Director and Agile Coach
    Sevatec
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Your progressive and efficient agile program can go downhill fast, and agile can get a bad rap, if upper management begins to think that the answers they used to get in the "Waterfall world" are no longer available to them in an agile world. Executives assume the team is managed poorly if they can’t produce artifacts they are used to seeing like fully resourced project schedules. They get frustrated when they can’t get a “straight answer” to questions they are used to having answered like “what is the project schedule’s critical path showing,” or “are we staffed properly to complete all the remaining requirements by the end of the contract.” They become unhappy with the team and possibly even start to see that “agile doesn’t work for our program” if they are told that they can’t get that information anymore in agile, or it isn’t clearly explained to them how to ask for the information they are really trying to understand.

    The answers are still there though the tools and methods are likely different. We need to be able to translate the questions being asked and help upper management understand how to better ask the questions to get what they are really looking for. Executives are responsible for ensuring the health of the program, that sufficient progress is being made, the program is within budget, the contractual requirements are being met, etc. Agile methods can leave executives uneasy because answers to questions regarding these can be “squishy” since user stories can be added and removed, they can use relative sizing techniques for estimation instead of specific hours, priorities can shift, and the customer’s needs drive much of the process decisions. By understanding what upper management really needs in order to be successful themselves, and how to extract that information using our agile toolset, we will be able to give them the data they need to continue managing the program and communicating its health to their leadership and customer counterparts. The goal for this session is to provide you insight into what is really being asked, to help your leadership better ask the questions “in an agile way,” and to deliver impactful answers derived from our agile toolset that allows for strong communication of the health of your program.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 years ago
    Sold Out!
    3 mins
    Talk
    Intermediate

    Creating an approach for change is difficult. There is a fine line between imposing an Agile adoption and creating a Transformation where people are collaboratively working together for the change. Based on my experience and in large US Federal Government organizations where imposed adoptions seem the norm, I’ve been working on combining many concepts into a transformation model that can work for large organizations that have ingrained cultures. This starts by helping the organization’s people take ownership and personalize what Agile means to them. Believe it or not, this can work.

    Intended for senior executives and their immediate staff (and the coaches that help them), the Taking Flight approach presents the importance of culture and how creating an organizational aspiration will help guide people. For large organizations, culture has been built up over decades and changing this is of the utmost importance to have an Agile Adoption stick. There are 3 main points I’ll address:
    - how to get people ‘onboard’ with a cohesive direction that they accept by collaboratively building their aspiration
    - how to develop and select strategies for incremental improvement towards the aspiration
    - how to realize changing from old routines into new ones aligned with the aspiration

    To help establish cohesive direction, I use an Aspirational model (your Guiding Star) to help organizations develop the direction they want to go. I show how the differences between an Aspirational model and an End-State. I explain that aspirations are inspiring and allow for a mindset change by not expressing the final state in terms of structure our expected metrics. From there, I discuss different techniques for assessing the current state of the organization and its people and developing strategies and actions for the necessary change management to move towards the organizational Aspiration; this is where the concrete steps come into play. Throughout this portion, I have the group try out various techniques for building an aspirational model and how to build the backlog of work to undertake the transformation. I introduce the Power of Habit as a means to help the organization undergo the necessary behavior changes. I close with a discussion to help the audience think around limiting change-in-progress and how to grow capacity to become more responsive to change.

    In this, you’ll get exposed to a few of many hands-on techniques that can be used to develop your Aspiration and execute on it. These are:

    • KrisMap
    • Business Model Canvas
    • Habit Loops
  • Liked John Hughes
    keyboard_arrow_down

    John Hughes - The value is in Being Agile, not Doing Agile

    John Hughes
    John Hughes
    Director and Agile Coach
    Sevatec
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Advanced

    “Being agile” is a mindset change.  You can’t “be agile” just by following agile processes.  Agile practices have intended benefit which you likely will not achieve if you just “do agile.”  Assessing the processes and practices to understand why they have been put in place, and what they are trying to achieve, will help you start to see how you can produce the intended value agile is meant to bring.  When you and your team can see the intended value of the practices then you can perform better as a team, deliver more accurately and more frequently, and please your customer and users much more consistently.

    We will explore agile practices such as the Scrum ceremonies, WIP limits, specific information radiators, etc. to assess what they are really trying to achieve.  Agile processes derive in part from psychological attributes and needs.  Humans execute agile delivery and to come together better as a team, keep our customers and upper management comfortably informed, produce what our customers and users really want, and consistently deliver high quality software, we need to fulfill our psychological needs and address our human factors.  This session will help you to understand what the intended goals are in these practices, what mindset changes may be necessary, and how you can ensure that your team achieves the value.  If your team is just “doing agile” then your project will likely wind up as another one that “was not well-suited for agile” in the eyes of your team, upper management or customer.  If your team can ”be agile,” then upper management will celebrate your success and your customers will applaud the efficiency by which your happy team routinely delivers the precise features they are looking for.

  • Liked David W Kane
    keyboard_arrow_down

    David W Kane / Dave Dikel - The Role of Architecture in Agile Development

    60 mins
    Workshop
    Intermediate

    In large Government and Commercial organizations with many interacting systems, architecture is necessary to collaborate effectively across disparate entities and systems. Traditional command and control approaches to architecture are often ineffective and cause great tension, especially when Agile efforts are part of the portfolio. We will discuss two principles, Vision and Partnering.  These principles provide insight and get results for both architects and Agilists; and present tools and approaches on how to effectively engage architects and architecture.

  • Liked Brandon Raines
    keyboard_arrow_down

    Brandon Raines / Judy Neher - No Way! Agile in the Federal Government

    60 mins
    Experience Report
    Intermediate

    There are so many challenges that organizations face. Healthy organizations continuously tool and re-tool themselves to go from good to great. This session will describe the road taken to transform a major government organization using Agile, Lean and Scrum principles, practices and techniques. From the contracting process to initiating, executing and closing projects, to redesigning the physical workspaces, and moving from a matrix to a team centric structure, this organization completely re-tooled how it did business, for the better.

  • Liked Kerri Sutey
    keyboard_arrow_down

    Kerri Sutey - Implementing Scrum Successfully on a Non-Software Development Project

    30 mins
    Talk
    Beginner

    A common misconception of Agile Scrum is that it can only be applied to software development projects.  This case study examines a DOD Modeling & Simulation project set in a Scrum environment and focuses on the roles, interactions and "rules of engagement" for all relevant stakeholders. Some of the key aspects that will be described are the critical importance of the team, customer involvement, frequent communication, and lessons learned. Executed properly, Scrum can transform the responsiveness, productivity, and quality of products and organizations. This work serves as proof that Agile can be successfully implemented in non-software development projects.