#NoProcesses - Getting More Done By Doing Less!

You may have heard about the #NoEstimates movement, and even #NoProjects. Both of those concepts challenge the assumptions behind two key aspects of delivering software. But what about the process itself? Do we even need approaches like Scrum, Kanban or XP - let alone SAFe, LESS, NEXUS, DAD - in order to be successful? Is following a pre-defined process helpful at all? Is there a simpler way to be effective?

This session examines the two key principles common to all successful software delivery approaches and builds out based on the experience of the participants. Like #NoEstimates and #NoProjects, the name doesn’t really mean to eliminate process altogether, but rather to build a process that works for your team, in your business domain, with your technology stack.

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Tutorial

This talk will be interactive, using the participant's experiences to identify key approaches to delivering software and how they can be applied.

  • Introduction - 15 minutes
  • Discussion - 30 minutes
  • Conclusion and Q&A - 15 minutes

Learning Outcome

They key outcome from this session is that a group doesn't necessarily need to begin with a "canned" process such as Scrum, SAFe, LESS, DAD, etc., but rather can start with nothing but two key principles and build out from there. The result will be a process that's completely tailored to each individual team or group and actually works with them rather than impeding them.

Target Audience

This session is intended for anyone with an interest in the process of delivering software. It will be of particular interest to managers and executives who oversee software development teams and programs.

Prerequisites for Attendees

There is no prerequisite for this session beyond an interest in how people work together to build software, and how to improve how they work.

schedule Submitted 1 week ago

Public Feedback

comment Suggest improvements to the Speaker