Best practise for change management

Question

HI i am working in small software company for a long time which is very weak in process. our company do the change in software when they get mail from client and we do not follow right process to keep the change management info some where. so please tell me best practise big and middle company follow to do the change management properly as a result later very easily we can find out the change management details. thanks

Afzaal Ahmad Zeeshan · Answer

There is a mind-set called Agile development as well as a bit complex process DevOps. The purpose of DevOps is exactly what you need. But it requires your team to properly work together with the client and that you keep listening from your clients in time. The thing about big companies is that they have several clients and they keep listening continuously and that keeps them focused on their work unlike hearing back too often which (as in your case) causes a lot of trouble as team itself looses focus on the problems features and bugs in the software. Secondly if all you need to do is store the information somewhere consider using some online services that manages your projects. Visual Studio Team Services is one of such services it is free for teams with less than 5 people; review the pricing here https://www.visualstudio.com/team-services/pricing/. Visual Studio Team Services would be a viable option here for you and also it would store all of your backlogs iterations and client-team communications easily. https://en.wikipedia.org/wiki/DevOps

Afzaal Ahmad Zeeshan · Answer

Agile itself is the basic concept in which the software development is primarily focused on the needs of the customers and not what our developers can build. Scrum or other methodologies are primarily just the way our teams interact and build the software. DevOps is a mind-set a philosophy a toolset which requires your dev elopment team and op eration s team to work together. The reason is that instead of having the development team waiting for the operations team to test deploy and then return with solution what happens is that you make them work together. In most cases Development team might be working in Agile Scrum or other strategies. However operations team would be working with their own style. The DevOps just merges them both together and instead of creating them separate 2 teams they work together as a single unit. This enables the teams to Ask for the user requirements Build for the user requirements Test the user requirements right before even passing the latest build Bring the user reports and test reports right in the development team so they can know what is wrong and what is required. Iterations can be set up by ops developers can look up and continue to work. Test systems integration systems are also available to developers and they can test them out and try them out as well. Developers don't have to wait for oeprations team and Ops don't have to wait for Dev team as well. But DevOps is a bit of complex concept to be implemented here or anywhere because it requires a lot of change in the currently implemented workflows of the system. But it can definitely save a lot.

tri_inn · Answer

@Afzaal thanks i know agile scrum is methodology but devops is also a methodology like agile scrum? when people would prefer DevOps over the agile scrum ? what is the difference between agile scrum and DevOps. please explain easy way as a result anyone can understand.