Is your software development team/organization (team) struggling? Has your team identified its failures, openly and honestly? If so, then your team is ready for solutions. There are literally dozens of frameworks or models designed to guide your team to success with a well documented prescription. They will even sell you an expensive training and certification product! Of those frameworks, a select few, are solid ways to create a team communication mechanism that works. The only real barrier is your teams commitment. You will find new boutique frameworks popping up all the time. Fancy, highly attractive jargon abounds. I find them all generally to be derivatives of the same old core human based method of doing stuff. In software we use the term systems[software] development life cycle (SDLC). Plan. Build. Test. Release. YMMV (i.e. – Plan-Do-Check-Act). You have to find something that speaks to your team.

When the rubber hits the road it may be YOU that is responsible for fixing your team. I hope that you find everything that you need to get started here at the Blogagility resource page.

Generally, I recommend that before you get started with any new process or “fix” implementation that your team have a profound understanding of what is broken first. And write it down. In big, public bold letters. I can guarantee the failure of any new process implementation in a team or organization that is not willing to put the effort into identifying, honestly and openly, its core destructive issues. Part of that organizational development process should also be to identify productive elements. Knowing your strengths and weaknesses will help you choose the appropriate mechanism for your “fix.”

Most everything that we discuss here at Blogagility is software centric. This does not mean that the methods are not able to be applied to other forms of work.

Recommended solution space for software teams

The industry is generally always moving very fast. Technology is growing at break-neck speed and the glue that holds the builders together has to keep pace. My current favorite, most efficient and effective, and recommended broad use process frameworks are Scrum, Kanban, and Scrumban. The application of the frameworks is dependent upon the type of software project work being performed.

  • “Scrum is a simple framework for effective team collaboration on complex projects. –”
  • Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members. In this approach, the process, from definition of a task to its delivery to the customer, is displayed for participants to see. Team members pull work from a queue. Kanban in the context of software development can mean a visual process-management system that tells what to produce, when to produce it, and how much to produce – inspired by the Toyota Production System[1] and by Lean manufacturing. – Wikipedia”

Defining effective use of any SDLC method or process

  1. It is effective when it is generating value for the team, the project, and the customer
  2. When the teams efforts are not generating value, the team is not effective
  3. Don’t blame the process and philosophy

Defining efficient use of any SDLC tool

  1. Your team process or method is only efficient when it is minimizing waste (*as compared to any other method)
  2. Waste must be defined, identified, and removed. Some waste is inherent to the system and can actually have value. (see: Coffee breaks!)