Retrofitting and Reworking in Agile

= Retrofitting and Reworking in Agile =

Sometimes in agile, the formatting and process of new documents and files are too dated for the current project. The team has to then rework and retrofit the documents to make them better suited for agile. It is not recommended to retrofit old documents, so if possible try to avoid it and create new documents using existing charts and reports. Transitioning to an agile framework will end up being a pitfall but sometimes those documents can be adapted to meet the current requirements. These can be a separate from the existing documents and can provide more leniency when switching to agile.

A charter can be transformed to rework existing pitfalls in the system. The milestones become high-level epics that the product owner can commit to delivering. As opposed to having a product manager the agile team can be self-organized which means one person doesn’t know everything about the project. You can either rework to fix part of the product or retrofit to rebuild part of the product. This adds a new level of quality in the development of the project.

Traditional agile practices avoid both reworking and retrofitting as it hampers the efficiency of the team. As the team moves forward and encounters problems they have the ability to deal with it or may have to spend more hours in the solution. Sometimes a project manager may have to discuss the project’s flexibility and if the changes are capable or not. The project schedule may be the hardest to retrofit. The schedule is a tool to deal with a thoroughly planned project. The product owner and manager should work closely in retrofitting the documentation with creating high-level milestones.

Through the triangle of responsibility there is equal share in how to retrofit the project’s documents. The reports made by the project manager, the product owner will still have some ability to change the organization, and the scrum master protects the project’s framework. Through this retrofitting can be useful in project management, so long as it does not make the team less agile.

= Citations = Rose, D. (2015, November 23). Retrieved November 27, 2017, from https://www.lynda.com/Business-Skills-tutorials/Retrofitting/175962/452774-4.html

Hertzfield, J. (2006, July 12). Retrieved November 27, 2017, from http://it.toolbox.com/blogs/alm-blog/agile-rework-and-retrofit-10467