Your current filters are…
User stories in the product backlog are just reminders for a discussion. This discussion that clarifies the necessary details takes place shortly before implementation only. But how are these details defined and how can you review after implementation whether they have been fulfilled.
Have you noticed that whilst everyone is talking about package management, fewer people seem to talking about the patterns and practices of package management, what you need to do to package up your application, and how well the tools out there support that. We'll talk about the packaging principles like Common Closure and Reuse Equivalencey, afferent and efferent coupling, and what main sequence diagrams show us.
Behavior-Driven Development is a way of building software focusing on application behavior. This is achieved by enabling a better communication between the customers and the development team and by using automated acceptance tests to describe the required functionality.
5th–7th September 2011