I’ve been invited to speak at Quicken Loans internal Developer Conference in Detroit. I’m really looking forward to it. We have settled on these two topics:
Agile software development starts with good requirements, just enough, just in time. So what does this really mean? Do we all have a clear vision of the big picture? How do we decompose stakeholder desires into workable chunks of meaningful work? And, when do we do it so we have sufficient detail without waste when things can change? Are we getting meaningful acceptance criteria from our stakeholders? What about estimates – at product conceptual inception, and throughout development? And, are you keeping your stakeholders engaged throughout development? We’ll address these questions and more as we help you get your arms around agile requirements.
Top 10 Dysfunctions with Scrum, Don’t Shoot the Messenger
Many organizations have tolerated inefficiencies and impediments for years. They recognize the need to become more agile; to respond to the needs of their customers and be competitive in the marketplace. They embark on adopting Scrum but struggle with successful implementation, often falling back on old habits when the going gets tough. Scrum quickly identifies these inefficiencies and impediments and requires their resolution. So, don’t shoot the messenger and try to change Scrum. This session will discuss a top ten list of common dysfunctions and help you deal with them effectively.