Are Agile methods appropriate for safety-critical products? This presentation describes how an Agile project in the nuclear industry, has managed to be Agile while maintaining nuclear safety. A related issue is the complex nature of the work, spread over multiple teams in multiple companies, with work projected to continue for over 5 years.
Parabol is an agile meeting tool that helps remote teams run guided retrospective, check-in and Sprint Poker meetings. Parabol’s structured format and built-in templates make it easy for facilitators to run a great agile meeting – no matter if you’re a pro or just starting out. It’s free to use for up to two teams.
There is plenty to fret about when you are running or on an agile team, but your measure of estimation should be one of them. In fact, despite what you may have heard from consultants or others, Scrum is not prescriptive about any particular estimation measure, let alone story points. Many practitioners support story points and it is been very in vogue for a while now, you should do whatever you and your team feels most comfortable with.
At the beginning of Agile, there was a tendency to aim at “pure” Agile, following the Scrum rules by the book. Even if there might be still Scrum cargo cult implementations, many Agilists have realized that Agile is more about continuous improvement and value delivery in a specific context than staying stand-up in daily status meetings. In this article, Mark Haynes discusses the Scrumban approach that borrows tools from both Scrum and Lean Kanban.
We constantly hear that change should be affordable and cost-effective with Agile. True, but, in reality, that is easily said than done. Complexity makes change hard. We cannot shy away from the hard problems posed by domains and business needs. So, how can we solve complicated problems without getting dragged into the quagmire of what appears to be an inevitable complexity?