Agile Testing
Test-First Reading List
ATDD (Acceptance Test Driven Design /Development) / BDD (Behavior Driven Development) / SBE (Specification by Example) Step Away from the Tools | Liz Keogh, lunivore
ATDD (Acceptance Test Driven Design /Development) / BDD (Behavior Driven Development) / SBE (Specification by Example) Step Away from the Tools | Liz Keogh, lunivore
Session Abstract:
Using examples in software development is a fundamental practice that increases developers’ productivity and software quality. However, in order to exploit their full potential, examples should be used habitually and correctly in an example-supportive environment.
The concept of process improvement has been around for quite a while. Many methods have been defined to conduct and pursue improvement. Then why isn’t everyone already an expert at it? We seem to never lack “improvement” content as if it’s fresh, and exciting-which it’s not. Maybe that’s because so much of what’s been espoused hasn’t worked. But why? Hillel Glazer examines several long-held assumptions about process improvement, proposes plausible flaws, and reveals new levels of understanding that have allowed breakthroughs in performance. Hillel looks at what happens when there’s too much focus on practices, when the underlying principles aren’t honored, and when basic values aren’t internalized. We see too much arguing over practices instead of working towards results; worrying about “compliance” instead of moving forward. What’s the relationship between values, principles, and practices, and why does it matter? Hillel explains it all in this compelling, entertaining session.
Continuous deployment is a process that encourages developers to push new code to production whenever they can. In this presentation, Itai will explain the principles of continuous deployment and will show how Outbrain can deploy code more than 20 times a day while serving recommendations to top publishers (including USA Today, iVillage, Boston.com, Chicago Tribune, Newsweek, TheStreet, The Boston Globe, and Slate. Hebrew: Ynet, Haaretz, TheMarker, Globes, City mouse, JPost and more).
Visualising System Archetypes – visualization and systems thinking
Many organizational challenges are a result of systemic issues, where cause and effect are not directly connected, but are separated by time and involve feedback loops and delays. Given that Kanban is a method for designing a software and systems development system, and systems thinking includes the idea of system archetypes that describe common patterns of behavior, we can use system archetypes to guide our visualizations and help us identify opportunities for improvement. This session will introduce how to understand system archetypes, describe a number of common and relevant archetypes, and discuss patterns that can visualize and thus help break those archetypes
More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level testing processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm and perceived as the main bottleneck. In the lecture we will focus on how we manage the testing processes across release lifecycle in complex environments when it is not realistic to finish all required work within a sprint, how to visualize and reduce testing batch sizes within sprints/releases, practical suggestions on how to deal with the testing bottleneck, how to deal with the mindset issues and last, how to run stabilization/hardening periods using Flow-based thinking.
A presentation By Ronen Bar-Nahor and Yuval Yeret @AgileIL12
Session Abstract:
Investment Technology Group (ITG) is the advanced stages of implementing an enterprise-wide Agile migration program, and wants to be able to monitor our implementation, both for the teams’ own benefit and for enterprise-wide governance of the migration.
As early as 2002, ITG has piloted the use of Agile for software projects. About two years ago, ITG decided to migrate all of its software development operation to a standard Agile process baseline, based on a mix of XP, Scrum and Lean practices. As part this migration, teams are starting to use Rally’s Agile Lifecycle Management platform. Having a critical mass of projects in Rally. We have started collecting from Rally a set of metrics which provides executives a quantitative insight into the progression of our agile implementation, and can be used by teams to continuously improve as part of their retrospection process. ITG has implemented a fairly comprehensive set of metrics, and plans to implement more based on teams input. These metrics are fairly generic in nature and can probably be useful to others as well.
Lecturer’s short Bio:
Sagi Smolarski is a Director, Software Development at Investment Technology group, leads the global initiative to implement agile and is part of the team creates ITG’s next generation enterprise infrastructure.
Sagi has been leading projects and development teams, and has previously headed the development of ITG’s flagship Execution Management system – Triton, developed by ITG’s first team to implement an Agile process (XP).
Sagi lectures at Ben Gurion University on Advanced Methods in Information Systems Engineering, a course which focuses on the Design, Architecture and Methodologies used to implement software systems, with a special emphasis on Agile methods. Sagi has been teaching Python at the High Tech academy. Sagi holds a BA in Physics from Technion IIT and a BSc in Materials Engineering from the same institution.
NOTE: Today Sagi is a Lead Coach and Partner at AgileSparks
How we do Agile without saying the word ‘Scrum’
During the last 9 months, Informatica’s B2B business unit transitioned to an agile product definition and development mode. Specifically, we selected Kanban as an agile development methodology. In this talk, I will cover our lessons from using Kanban for enterprise software product development, including:
The impact of a cross-geography organization.
Kanban board structure and changes to the board as a learning process.
The use of data that is collected from the board.
Why we decided to introduce the notion of iterations to our Kanban implementation.
In this talk Roy Osherove will discuss the idea of Elastic Leadership, and the role of the team leader in the age of agility. Roy will cover his Team Leader’s Manifesto, and the three maturity phases teams go through on the road to self organization.
Request for additional information and prices