Author Description

Software Development and Software Maintenance are distinctly different, with respect to the nature of work and execution of these activities. The work types, work sizes, workflow, required skills, and work stages are all different in Software Maintenance. The execution models that are in practice are primarily devised for software development work, and passed on to maintenance teams with the assumption that the work is similar. This mismatch in execution models has made Software Maintenance inefficient and ineffective. Therefore, it is prudent to look at the needs of Software Maintenance, and devise models, processes, and practices that suit its requirements.All these challenges pose great hurdles for Software Maintenance teams; they frequently stop and start work, switch contexts from one work request to another, and try to traverse the work requests through several silos of cross-functional teams. Over time, several execution models have evolved to address these challenges. Most of these follow agile and Lean methodologies. The model discussed in this publication is called Scrumban, a hybrid version of Kanban and Scrum. This version leverages the features of both models to Stop Starting to keep the work in progress at the minimum and Start Finishing to reduce the end-to-end lead time. This publication describes five steps to implement Scrumban in any Software Maintenance project.Who this book is for:This book is primarily written for anyone working on Software Maintenance projects - project managers, team leads, process coaches, technology analysts, designers, programmers, testers, and other change agents of the software engineering process groups. Just to make it simple, if your answer is "yes" to one or more of the following questions, then this book is for you:1. Is your Software Maintenance and Support team always working on high priority work items?2. Are there work items which need to be delivered on time without being impacted by unplanned and emergency wor