Rob Scherer and Rob Alford discuss the Design Sprint process used by Google Ventures, some of the changes made to it and lessons learned along the way.
Owais Zahid talks about establishing quality requirements for products, including quality aspects in the definition of Done, and communicating goals with the development team.
Paul Payne explains the benefits of containerization of a Go web service, discussing testing, integration, canary deploys and how they achieve 20 minute development cycles with zero downtime.
James Shore proposes to take a step back and ask what is the purpose of Agile practices, what brings success and what doesn’t, and what it takes to be successful with Agile.
Alex Baldwin explains the exercises used in the 5 phases of a Design Sprint: Build, Diverge, Converge, Prototype, and Test.
Chris Smith provides practical advice for sprint retrospectives, gathering information and identifying root causes of both problems and successes, and addressing issues from a different perspective.
Michael Sahota discusses top 10 Agile gotchas: when release is ready, sprint meetings take too long, no retrospectives, people aren’t working together, getting new stories, stand-ups are boring, etc.
Sprints, Scala, Scale & Serendipity: Blue Sky Thinking and Washing the Pots on the Road to Success at a Technology Startup
Ian Brookes and Rob Strange recount the journey and relationship of a Tech start-up and its software development partner, with the milestones and millstones along the way.
Chris Nodder shares tips for getting a product vision, a high-level design, and a plan for the first sprints of a new product in one week.
Janne Jul Jensen presents the development process of a mobile banking application from prototyping to the actual product including SCRUM sessions, sprint evaluations, UI designing, and user feedback.
Karthik Dinakar presents a case study showing that trying to reach short-term goals by ignoring some practices can lead to long-term failures, how they recovered and recommends some best practices.
Kelley Horton discusses the reasons why her organization transitioned to Lean-Agile, the approach used and the visual tools helping them minimize WIP, concluding that visibility leads to success.