Scheduling should be done independent of and orthogonal to workflow. In fact, you don’t have to create a schedule for a flow system. It will flow all by itself, and work will flow much faster and much more reliably than it could possibly follow a schedule. But take a closer look at that workflow: Just when you thought it was obsolete, the V model reappears. This talk will step through systems design, approval processes, and scheduling, development workflow, depolyment, from a completely different angle.
One of the most common questions asked of practicing Agile teams is:
How can we increase velocity?
Many teams have had to answer this question, but is it the right question? Velocity is an excellent measurement for determining project timelines and progress towards them but doesn’t give us any indication about the overall value of the features being delivered. All too often poor prioritization and solutioning are ignored because velocity is the KPI for the team. This session shows how to use value as a tool to ensure that you get more of the right things done.