Emily Bache
Emily is an experienced software developer, trainer and conference speaker. She is currently an independent consultant specializing in training and coaching in agile engineering practices. With over a decade of experience working in agile software development projects, expertise in languages with both dynamic and static typing, and having worked at companies ranging from large corporation to small startup, Emily is uniquely placed to understand the needs of software development professionals from diverse backgrounds and technology areas.
Track abstract - Testers - J2
Working effectively as a tester on an agile team
In a traditionally run project, the focus is often on executing detailed manual test cases. In an agile project, you might invest more heavily in test automation, together with manual exploratory testing. In a more traditional method, testers put in the greatest effort in the weeks preceding release. In an agile environment, they are expected to do testing throughout development. In a more traditional environment, testers can rely on requirements documents when designing test cases. In an agile team, they can expect to spend a lot more time in face to face discussions about what the system behaviour should be. How do you as a tester adapt? What new skills do you need?
Our expert panelists will talk about their experiences and how they deal with these kinds of issues as testers in an agile team. The discussion will be open to questions and comments from the audience, so do come along and take part.
Track abstract - Software Development Teams - G4
The most important decisions the team should take
When moving from a command-and-control culture to self-organizing teams, there is often confusion about what decisions should be made by the team, and which decisions stakeholders outside the team should be able to dictate. What are the most important questions the team should get to decide for themselves?
The time of day for the daily standup meeting? The delivery dates for the product? Which IDE to use? Who should be on the team? The definition-of-done checklist? Whether to base the architecture of the system on x or y framework?
This discussion will draw on the experience of the four expert panelists, who will share stories and advice based on the teams they have worked in. The audience is welcome to take part, so bring your most important questions.
