Scrum, Kanban & Extreme Programming Methodologies For Team Work

There are three methodologies exists for agile based methodology, which are Scrum, Kanban and Extreme Programming. We are going to explain about Scrum methodology, which is mainly used by cross-functional teams to develop new products. In this methodology, the deliverables are the product features not the product itself. The ultimate goal of using scrum is to deliver highest values to the customer. Each stage or process known as sprint. Software companies mostly adopt scrum because they do not have exact final product and in that industry, there are more chances of change management at any stage.

Other industries similar to software companies such as data clouding also use Scrum methodology

Agile - based methodology

It Is structured as Analysis, Design, Built, Test. In each iteration or sprint firstly whole team analyse the new process and then they design what they going to do. After that they built the software or product and last phase is the testing phase.

Project life cycle

Used in this methodology is iteration based because there are sprints in the scrum methodology and those sprints are similar to iterations in which every time at the end of iteration or sprint stakeholders review the process and also re-evaluate priorities. Each sprint adds new capabilities and the goal of each sprint is to develop workable product The Project manager in Scrum methodology is known as scrum master. He is different from usual project manager because unlike of project manager, scrum master has no authority on the team or on process. He can not call somebody to do particular task but could propose a new sprint at any time and team must satisfied with him to do so.

Strengths of Scrum methodology

It gives more transparency, project visibility it means everybody knows who is doing what, and it further reduces mutual misunderstandings and confusions. Moreover, it increased team accountability, which makes them self-dependent to decide what to do and time to do and amount of work to be done in each sprint. It also enables the team to accommodate changes easily and saves money by fixing small errors.

Weakness of Scrum methodology

The weaknesses of above mentioned technology are mainly the scope creep because sometimes they do not have exact end date and because of that stakeholders may asking to add more functions to the product. Lack of experience and commitment is sometime creating a major problem in Scrum because there is a scrum master instead of PM and he has no authority over the team.