This document discusses how agile frameworks like Scrum, Kanban, and Agile can be applied to software maintenance and support projects. It notes that software maintenance involves modifying existing software to improve performance, adapt to changes, or address change requests. Kanban focuses on visualizing and improving any workflow, using cards to signal steps. Scrum defines how to execute agile protocols through daily standups, modeling complex defects, and using information radiators and retrospectives. The overall aim is to visualize work, limit work in process, focus on flow, and continuously improve through techniques like mapping tasks and addressing bottlenecks.

1. Scrum/Agile/Kanban in Support
or maintainance Projects
Presented by
Ravi G

2. What is Software maintenance ?
 Software maintenance is defined as the process of modifying a existing software system or
improve performance or other attributes, or adapt to a changed environment
 or even take few Change Requests
--- Ravi G

3. Agile or Kanban or scrum
 In layman's term...Agile is protocol, a book, while Scrum defines execution for that.
 Agile is really specific to shipping and iterating on software, whereas kanban is about visualizing
and improving the workflow for any process.
 Kanban is Japanese for “visual signal” or “card.” Toyota line-workers used a kanban (i.e., an actual
card) to signal steps in their manufacturing process. The system’s highly visual nature allowed
teams to communicate more easily on what work needed to be done and when
--- Ravi G

4. Kanban
 A picture is worth a thousand
 words for scientific reasons
 Eg:-Trello story boards can be used
--- Ravi G

5. Balnced work load
Eliminate waste
Measures velocity of eam
--- Ravi G

6. --- Ravi G

7. How to get 0 tickets ? The whole aim
 Visualize the work || Limit the work in process || Focus on flow || Continous improvement
process to be followed
 Map the tasks in to a flow chart as below
 TODO || Ongoing || Done || or anything that interests
 Now look into the bottlenecks
 Train clients to avoid unnecessary tickets
 Bug reports / story cards
 let the Customer/client prioritizes the bugs
 Create a Common bug tracking database
 QAs test and write functional acceptance tests
 Developers write failing unit tests
 Repetitive bugs should be avoided- Document them for a Quick fix
--- Ravi G

8. Scrum Team- We are all to-gether
No developer/architect/designer/tester
1. Daily Scrum meetings -Calls
2. A Scrum of Scrum - We are all to gether
3. Modeling days while solving complex defects - Documentation plays vital role
4. Information radiators displaying InProgress, completed, reopened, closed defects and other
information - use indicators which explains all
5. Usage of Wiki for collaborating with the customer/clients- increase ongoing engagements/strengthen
Member relationships
6. Review and Retrospective
teams maintaining and supporting websites must pay attention to the Service Level Agreement or SLA
with the customer. This usually spells out the turnaround time (TAT) within which the agency
 Quick fix is often used in emergency, corrective maintenance. Emergency maintenance is unscheduled
corrective maintenance performed to keep a system operational
--- Ravi G