Agile software development
There often seems to be a tension that surfaces between the process (that which guides us) and the execution (that which we do). Agility and architecture also play out in this same way, and it can be a very destructive. Yet, each side needs the other to exist. In this …
We measure project success by the team’s ability to efficiently and reliably deliver valuable, high quality software to the customer. Increase the prospect for project success by ensuring team members have the skills for effective collaboration and clear, unambiguous communication. Diana Larsen will describe the six collaboration skills teams need …
With the craftsmanship movement, focus has shifted from viewing the developer as a production unit to viewing the developer as a craftsman with responsibility and individual skills. Agile can’t afford heavy processes to control developers. To be lightweight an agile process needs a structure of craftsmen that take responsibility for …
This video proposes a conflict model that helps teams chart a course through conflict and turn it into a force for greatness. It walks you through five levels of conflict from “Problem to Solve” to “World War,” with each step finely tuned to view conflict in a deeply human and …
INVEST is an acronym that you can use to remind the important attributes of great user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable. [youtube L_NyCczp0Fk]
Most of us have worked where there’s tremendous effort on planning, anticipating the needs of our customers, testing before release to our customers, re-thinking, re-considering and re-coding. To a developer, the only thing that may seem worse is when there’s none of this. Regardless, we expect to know, in advance …
