DevOps East 2017 - Business Analysis & Requirements
Thursday, November 9
Design by Discovery to Stop Building Bad Software
Two common situations lead to bad software—the project team isn’t aligned on the problem or the customer isn’t involved in the design process. Either way, you end up with a product that the business didn’t ask for, the tech team struggles to deliver, and customers don’t want. So, how do you increase confidence in the direction of your product and work together to build innovative solutions that bring the business, technology, and customers together? Garren DiPasquale and Matt Wallens introduce, a process to understand business goals and customer needs. It isn’t about designing screens or...
Putting the “Story” Back into the User Story
If you're using user stories for your agile requirements, you're not alone. They seem to have become the ubiquitous vehicle for communicating customer requirements to agile teams. And they work incredibly well in this regard. However, many teams are experiencing problems with them. Bob Galen does not believe it’s the story’s fault. Bob says we often forget the “conversation” part of the story—and more importantly, the storytelling part. When Kent Beck first described the idea of the user story, his original intent was to initiate or inspire a story-level conversation between a stakeholder...