Which practice is this?
In theory, retrospectives are the heart of agile methods, the reflect and adapt cycle that fuels continuous improvement. In practice, many leaders encounter passive resistance: the teams find them a painful waste of time. How can we get the real world benefit without the pain?
Patient, “It hurts when I do retrospectives. Retrospectives suck!”
Doctor, “Then stop doing that!”
Patient, “...OK, then what should I do instead?”
This session answers that question. Learn a simple system of practices that give retrospectives clear purpose and yield these additional benefits:
Prerequisite knowledge:
Basic familiarity with iterative planning (Scrum's sprint planning, XP's planning game, etc.)
Optional: painful retrospectives or ineffective follow-through on retrospective action items.
You've seen and used personas on projects before, but did they really add the value you desired? This session will be a hands-on workshop exploring how and why we use personas. We'll get practice creating personas for a fictitious project. At then end of the workshop you'll have experienced how to effectively bring a human element to your project through personas.
Creating a product without a shared vision is like trying to read a sign without your glasses. There's a lot of squinting and guessing as to what the sign says. Where one person sees an E another might see a T. In the end, no one can agree on what the sign says and everyone has a headache.
Having a poor vision or no vision at all almost guarantees poor results for your product. The stakeholders won't get the value that they need or expect, the team won't know why they're building the product and no one knows what success even looks like.
In this workshop you'll learn how to create a product vision board - a simple, visual tool for defining the goal of the product and the path to achieve that goal. We'll look at why we need a common vision, how to create the board and how to validate the board so you know that you're on the right track. Get your glasses on and let's bring our product vision into focus.
Learning Outcomes:
Test-Driven Development is an important design and problem solving technique that helps software developers improve product quality and the quality of their life. How? By preventing defects and by giving you warning when your design starts to deteriorate. The tests created during TDD also give you the freedom to change your mind and safely evolve your design.
This tutorial describes the problems addressed by TDD, as well as the additional challenges and benefits of applying TDD to C, C++ and embedded software. You'll also see the latest ideas, techniques and tools for creating fakes, and mocks in that help you make sure you know what your code is doing. This won't be just show and tell. Bring a laptop or tablet and you can get your own first hand experience at TDD.
