When it comes to software development, business stakeholders want to know what valuable features are going to be created, and when to expect them. Engineers want to deliver valuable features by writing quality code at a sustainable pace. In many organizations, these are incompatible goals because of the way the delivery process is implemented.
In this poster session, I explain why that's the case, how software engineering is different from other types of non-trivial business projects (and why that matters), and how to set up a software delivery process that maximizes the value of releases while satisfying the needs of both business and engineering. I'll also talk about the commitments each side has to be willing to make in order for the process to work, and some of the special considerations around delivery in large, grant-funded software projects.