Agile + DevOps West 2022 - Agile Practices
Wednesday, June 15
Adept Agile Requirements – Plan Faster, Better & Easier
For a philosophy built upon the idea of rapid adaptation, the rigid way in which requirements are managed in many agile projects is a poor fit. For instance, strict requirement trees linked tightly to organizational hierarchies can be damaging to local ownership, speed, and quality of decision-making. Potentially useful ideas like user stories and Gherkin can be misapplied to ill effect. A narrow focus on writing out requirements can miss opportunities for more effective communication through visualization. This workshop will review a host of simple but lesser-known techniques for...
ScrumBan – Effectively Combining Scrum and Kanban
PreviewTeams using Scrum sometimes struggle with operational or emergent work blowing up their sprint plans. As DevOps delivery is increasingly used by organizations the need of Scrum teams to accommodate operational work also increases. After all, it does not matter how interesting that new feature is if production is down. By combining the disciplines of Scrum and Kanban teams can find that happy balance of planned work and emergent work while still maintaining discipline and continuous improvement. As an example, we will build up a hybrid process for a hypothetical team to discuss the...
Thursday, June 16
Is Agility Even Possible in Implementing Commercial, Off-the-Shelf (COTS) Systems?
PreviewMany individuals who have worked as part of an initiative to implement off-the-shelf systems have heard that agile approaches can’t work - that agile only works when building solutions from scratch or adding functionality to these systems. We believe and have seen, that agile approaches are actually preferable to a traditional waterfall in these instances, and the differences between proprietary and customization of commercially available system development have more in common than not.
Measuring Long-Term Productivity: The Developer’s Legacy Index
Measuring a programmer’s productivity is a problem as old as the software industry itself. Number of worked hours? More productive people should need fewer hours, not more. Number of completed tasks? Not all tasks are equally hard. Number of introduced bugs? Bugs are not necessarily the programmer’s fault, and besides, what constitutes a bug anyway? The closest we’ve ever got to measure a developer’s productivity is lines of code, and this has proven to be a poor metric because not all lines of code are equally valuable. However, if we could measure not just how much a developer writes but...
How to Create a Product Office
Whether you’re researching market opportunities, brainstorming new product ideas, developing products customers love, or managing product roll-outs – organizations face many challenges in product delivery. In this session Dave explores the Product Office and how it helps organizational alignment across teams, oversees service delivery, and provides visibility into development.