Being Test-driven: It's Not Really About Testing
Good news: Test-driven practices have jumped the chasm to general acceptance! The bad news, though, is that while TDD, BDD, and ATDD are prominent buzzwords in the industry today, they are rife with misconceptions, with many people incorrectly assuming that being test-driven is all about testing.
In this talk, learners will leave with a clearer understanding of Test-Driven Development (TDD), Behavior Driven-Development (BDD), and Acceptance Test-Driven Development (ATDD), and gain practical insights into how these practices can help teams develop better software. We will gain an appreciation for TDD as being primarily a specification and design technique, and how to get the whole team involved earlier in the delivery cycle using a BDD approach.
Outline/Structure of the Talk
- Short experiential activity (99 Test Balloons) to start the session (5-10 min)
- What is Test-Driven Development (TDD)? (10 min)
- What is Behavior Driven-Development (BDD)? (10 min)
- What is Acceptance Test-Driven Development (ATDD)? (5 min)
- From test-last to test-driven (5 min)
- Q & A (5 min)
- Self-correcting worksheet on concepts discussed as take home activity
Learning Outcome
- Understand the essential ideas behind being test-driven, and what problems it aims to solve
- Gain a better understanding of TDD, BDD & ATDD in practice and how they complement one another
- Reimagine our thinking about how we write tests
- Discern why being test-driven is more about specification and design driven through tests, rather than testing after something is produced
- Understand how the whole team can get engaged early and often in the process and enable better understanding of the essential aspects of the system to be built
Target Audience
Programmers, test engineers, analysts, product owners, and others involved in building software products seeking to better understand the essential ideas behind test-driven practices, what problems they aim to solve, and practical insights on how to get started
Links
Yo! What’s The Scenario? AgileDC, 2018
https://www.slideshare.net/RajIndugula/yo-whats-the-scenario
Be Ready, Be Done: The Art of Slicing Stories, Agile India 2017
https://www.youtube.com/watch?v=hR3hiPW7lH0
schedule Submitted 2 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Sanjiv Augustine - Driving Flow, Value, and Innovation with the Agile VMO™
45 Mins
Keynote
Intermediate
Historically, Project Managers (PMs) and other middle managers have hustled in a bureaucratic system to drive teams to deliver value. As organizations transition from a project to product model, where can these leaders best add value in a fast-moving, Agile and entrepreneurial world? In this new and exciting world, middle managers are enabling rapid delivery of value and successful business outcomes via the creation of the Agile Value Management Office™. Learn how an Agile VMO™ drives business agility through small batches, frequent releases, and continuous adaptation. We'll explore how to:
- Create a collaborative management team-of-teams
- Bring Lean discipline to product portfolio prioritization
- Establish an End-to-End team model of resource management
- Track in-flight product work using a Visual Management System
We'll explore the transition for PMs and other leaders into this exciting role: facilitating the delivery of flow, value, and innovation end-to-end on the Agile VMO™, even as they support their Agile teams in the quest for business agility. -
keyboard_arrow_down
George Dinwiddie - Making sure the submission system is open
George DinwiddieAgile Consultant & Coach, Co-Founder of AgileDC ConferenceiDIA Computing, LLCschedule 3 years ago
10 Mins
Lightning Talk
Executive
Just testing in production
-
keyboard_arrow_down
John Tanner - Using Metrics for Good not Evil or: How I learned to Stop Worrying and Love the KPIs
45 Mins
Workshop/Game
Beginner
Using metrics for punitive reasons is a problem as old as time. In software, this is further complicated by the fact that people rarely agree on why we are collecting metrics in the first place. In this session we will explore how we can use metrics for good instead of evil.
By focusing on the goal of system improvement, rather than individual performance, we can begin leveraging data to make a positive difference in how we work while also delving into why we work the way we do.
This session will include real-world examples of problems that organizations create for themselves by using metrics for the wrong intent. We will also discuss examples of good metrics and how they can be used to make our lives better.
-
keyboard_arrow_down
John Hughes / Tara Lemieux - Value-driven CMMI: An Agile Approach to CMMI for Agile Companies
45 Mins
Talk
Beginner
CMMI and agile haven't shared many beers at the bar over the years. But there is no reason they shouldn’t be best of friends. They both long for continuous improvement, creating learning organizations that strive to reduce risk and increase quality. I believe that a major cause of dissonance is the lack of perceived value in the way the CMMI models have been applied and appraisals performed in the past.
So, what would it look like to implement CMMI and prepare for an appraisal focusing all of our effort into creating value and removing waste, instead of adding it? That was the question we tackled this past year and are seeing a completely different practice and outcome given our approach, including enthusiasm and appreciation from the project teams for this approach as opposed to the more typical dread.
Participants in this presentation will hear from both a CMMI Lead Appraiser and an agilest who lead this value-driven approach to CMMI. They will learn how agile mindset, practices, and tools can be used to apply the CMMI model to our delivery, with intentional focus on creating an ever-maturing practice that reduces risk and increases quality. Participants will also hear how agile was used in the appraisal preparation, enabling continuous improvement across the organization and even reducing the amount of time and effort needed for the SCAMPI A appraisal.
-
keyboard_arrow_down
Derek Huether - 10 Steps to Better Outcomes by Using Metrics
45 Mins
Talk
Beginner
This session is not intended to offer an exhaustible list of metrics or instructions on how to improve all systems. Rather, the intent is to provide a framework on how to ensure the quantitative and qualitative metrics you use are measuring the right things and how to apply them to a system of continuous improvement. Attendees will have a repeatable framework they can apply after leaving the session.
The session is broken into two main parts.
- Part 1: Identify the right (quantitative and qualitative) metrics that will help people and teams meet outcomes or goals.
- Part 2: Create a cycle of learning and improvement that aligns people and teams to the outcomes or goals.
-
keyboard_arrow_down
Ben Scott - Instilling a culture of craftsmanship
45 Mins
Talk
Beginner
When companies are struggling to increase the quality of their deliverables they tend to turn towards quick technology fixes, for example pushing for more test automation. The real solution isn't a technology fix but a cultural one. We need to change our culture to one that embraces, nurtures and encourages software craftsmanship.
It's only when your employees care about the quality of their work and when your organization rewards quality over speed that you'll make a lasting impact. Let's explore what this means and how we can start this culture shift.
Some of the things we'll look into:
- How to implement code reviews that become primers for mentoring each other.
- How performance reviews can impact the quality of your software
- How a CICD improves software quality
- Changing your management style towards Management 3.0
-
keyboard_arrow_down
David Fogel / David Bujard - Nine levels of Agile Hell... and how to get out!
David FogelAgile ProfessorDefense Acquisition UniversityDavid BujardAgilist, CoachBlackstone Technology Groupschedule 3 years ago
45 Mins
Talk
Beginner
Government Agile transformations can feel like overwhelming efforts – but do not abandon hope! This interactive, audience-driven presentation reviews how government and large organizations ESCAPE common Agile adoption challenges.
You - the audience - will prioritize your pain points; we’ll focus on the five Agile hells most highly prioritized. We will discuss real examples of “escaping” out of each Agile hell, with pro tips and success patterns you can apply.
The Agile hells we've escaped include:- No Transformation hell - A federal program or department wants to change but can’t start or can’t finish
- Too Fast hell - Newly Agile federal programs sometimes respond TOO rapidly, too often changing priorities.
- Technical hell - Programs can become bogged down in technical debt and manual processes.
- No Trust hell - Government delivery can be slowed by lack of trust between contractors and feds, between business and IT, or between compliance and delivery groups.
- Product Owners hell - Government Product Owners can be unavailable, think they are managers, aren’t empowered to provide vision, or struggle with prioritization
- Too Big hell- A frequent pattern in federal Agile! Large batches produce slow progress, low visibility and high complexity, seen in big programs, big deployments, and big contracts.
- Collaboration hell - Government teams can struggle with collaboration within the same organization across roles and across the fed-contractor divide.
- Stove-piped hell - Government organizations can struggle to collaborate across contractual or organizational boundaries within the same enterprise
- Leadership hell - An organization can only be as agile as its leadership. In the government, how can you work with leaders who aren't ready to be agile?
For each Agile hell, we focus on successful techniques to escape from these common dynamics. Unlike other presentations, we won't be doing a deep dive, but we will cover the most important challenges our audience face.
-
keyboard_arrow_down
M. Scott Ford - Building a Bridge to a Legacy Application - How Hard Can that Be?
45 Mins
Experience Report
Beginner
My team was asked to build an integration with an old legacy application which had no programming API whatsoever, and we were so excited. How did we tackle that challenge? Did we succeed? What happened next? Come and listen to find out. And I promise the ending will surprise and/or depress you.
-
keyboard_arrow_down
Tyler Grant - Words Matter: Building Trust and Dropping Jargon to Create Stronger Teams
45 Mins
Talk
Beginner
Within the Agile and technology communities, it can be easy to assume that the language we use every day is common knowledge and shared throughout our professional spaces. Certainly when we interact with other professionals and hear them using the same terms, this just reinforces our assumptions. Especially when we leave the boundaries of technically specific language and enter the realm of jargon or “buzzwords” it can be easy to find validation through other people’s language preferences.
However, using this type of language can not only create divisions within our teams, it can obfuscate meaning, delay action, and create misunderstandings that can inhibit a team's ability to deliver. By examining the differences between jargon and technical language, we will look at how this use of language can create in- and out- groups and break down trust within an organization.
By committing to using broadly understood language and being direct in the way we interact with each other, we can improve our ability to perform at a high level in the fast paced technology space.
-
keyboard_arrow_down
John Hughes - Improve Your Agile Transformation Success by Applying the Lens of Spiral Dynamics Integral (SDi) and AQAL
45 Mins
Talk
Intermediate
Changing the practices, behaviors, and beliefs of people and teams is hard; and organizations are many multiples harder. As agilest, we are educated to seek and deliver value. But that is one of the first big issues. What are the chances that we can know what is truly valuable for the people within the team or organization, both individually and collectively?
Another big issue is that most agilists are well-educated in frameworks, practices, and tools, but our training doesn’t generally prepare us for the other aspects imperative to implementing lasting agility and change. There is little focus in our standard training on the impact of systems and structures, and even less on internal aspects such as morals/ethics, ego, psychology, and culture.
I would like to present to you two models which opened my eyes over the past 6 years to a much larger awareness and understanding of how to approach agile transformation for impactful lasting change, and show you how to apply them to your work efforts. Seeing people, teams, and organizations through the lens of these models has greatly changed my understanding and approach and I believe has strongly benefited the outcomes of my efforts.
Spiral Dynamics Integral (SDi) is a bio-psycho-social developmental model showing itself through color bands representing levels of increasing inclusive evolution. AQAL – All Quadrants, All Levels [All Lines] – models a set of quadrants depicting our internal and external, individual and collective attributes and aspects. Woah! Don’t be thrown by that crazy-sounding stuff. Stick with me.
While those models might not sound very applicable to decreasing your cycle time to deliver your latest microservices through your fully-automated DevSecOps pipeline, without awareness of these models, you may never actually lead your team(s) to the point of decreasing cycle times, much less get your organization to the point of benefiting from DevSecOps practices.
Please join us for this session as we explore how these models allow us to be more successful in our work as Scrum Masters, Coaches, and/or Leaders. Benefit from learning new ways to see your system, avoiding and removing challenges and impediments you face in your sluggish, stuck, or failing agile journeys. Begin to see the world in a whole new way, not just at work, but in all aspects of life.
-
keyboard_arrow_down
Allan Guyet - The Agile Coaching Secret Sauce - Being Intentional In All Things
45 Mins
Talk
Beginner
We all know the Agile Frameworks - Scrum, Kanban...they are on the web for all to see, but what brings Agile to life? In this discussion, Allan Guyet, Agile Coaching Practice Leader, will discuss how "being intentional" in your role as a coach will 10x the performance of your Agile teams and create excited teams and customers.
Geared toward new Coaches but with plenty of tricks for veterans, Allan will share his experiences on how "being intentional" helped prioritize features, build trust with stakeholders, and shift mindsets. Filled with his classic anecdotes and analogies, the stories will make you feel like you were there.