The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects.In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories.
Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up-front and how much to do just-in-time.
Agile software development was born ten years ago, with a gathering of industry luminaries in Snowbird, Utah. They were frustrated that so much ceremony and effort was going into so little success, in failed project after failed project, across the software industry.
They had each enjoyed amazing successes in their own right, and realised their approaches were more similar than different, so they met to agree on a common set of principles. Which we promptly abandoned. The problem is that Agile calls for us to embrace uncertainty, and we are desperately uncomfortable with uncertainty. So much so that we will replace it with anything, even things we know don’t work. We really do prefer the Devil we know.
Over the last year or so Dan has been studying and talking about patterns of effective software delivery. In this talk he explains why Embracing Uncertainty is the most fundamental effectiveness pattern of all, and offers advice to help make uncertainty less scary. He is pretty sure he won’t succeed.
Description: As developers build larger and more complex systems supporting many users collaborating on growing data-sets in parallel, many are turning to patterns like Command/Query Responsibility Segregation (CQRS). Unfortunately, the baggage of building N-Tier style business logic continues to weigh on their modeling efforts, often resulting in domain models that don’t handle consistency correctly in the face of race conditions. Join Udi for a new perspective on CQRS using a new twist on the saga pattern.
GitHub.com is the place for open source developers to collaborate on their projects. But there's a perception that GitHub and Git are the domain of Mac and *nix users. Not so! In this talk, Phil Haack, a GitHub employee, will show how GitHub makes open source collaboration fun and tools and techniques for using Git with GitHub on Windows.
Roy Osherove, author of "Notes to a software team leader" and 5whys.com , talks about the role of the software team leader in these semi-agile times. What is the purpose a team leader serves? How can they achieve their purpose? How is fear a factor? These and more will be answered in this talk that every future and current software team leader, and other leadership roles (architects) needs to hear.