Agile process Kanban.

 Agile Process

          Many of the Agile ideas surfaced in the 1970s. Studies and reviews were conducted on the Agile Method that explains its emergence as a reaction against traditional approaches to project development. 

           A sprint is a period of time allocated for a particular phase of a project. Sprints are considered to be complete when the time period expires. There may be disagreements among the members of the team as to whether or not the development is satisfactory; however, there will be no more work on that particular phase of the project. The remaining phases of the project will continue to develop within their respective time frames.

 

Kanban

Method for managing the creation of products with an emphasis on continual delivery while not overburdening the development team is called the Kanban. Kanban is also like the scrum, it is a process

designed to help each other to work together more effectively. Kanban is mainly based on three basic principles.

1. Visualize what you do today (workflow):
   Items in the context of each other can be very informative. It is allowing a better understanding of the work and the work flow.

2. Limit the amount of the work in progress (WIP):
   This helps to balance the flow-based approach so teams don’t start and commit to too much work at once. It advices the limiting work in progress, it is also reduce the waste from multitasking and context switching.

3. Enhance flow:
   After something is done, the next height thing from the backlog is pulled in to play.

Kanban always let the path to meets the needs of the customer and the work. And also kanban has six main general practices.

1. Limiting work in progress
2. Flow management
3. Visualization
4. Making policies explicit it
5. Feedback loops
6. Collaborative or experimental evolutions

Kanban has many benefits.

         1. Kanban reduces the waste and the remove the activities that don’t add    value to the organizations , team or department.

         2. Kanban empowered the higher performing team members. And also  improve the chances of more motivated.

         3. Kanban delivers the features faster than others.

         4. Requires fewer teams to setup changes to get started.

          5. Kanban is balancing the demands.

Kanban can be used in many different areas, it can be implemented in various ways. But the overall process stays the same from project to project.

According to the particular task, different development stages can be determined. The primary requirement is to divide the project into three big parts: “To Do”, “In Progress” and “Done”. Here’s an example of how the software development process can be divided:

1. Product backlog
2. Requirements
3. Design
4. Development
5. Testing
6. Deployment
7. Done

What is Kanban methodology?

“Kanban” is a word of Japanese origin. It consists of two words: “Kan” – visible; and “Ban” – board.Therefor to get to know about the kanban board is very important.

     The kanban board is an intuitive way of your project representation that allows tracking the current status. During this phase, every task gets its priority level. You can create your Kanban board using trello.

Given below is a diagram of a kanban board

 

Disadvantages of the kanban.

1. Keeping the Kanban resized as demand changes can be slow and difficult to manage.
2. Lost hard copy tags/forms and Kanban cards. As these are integral to the Kanban system loss or damage to them may result in process difficulties. To compensate for this a variety of electronic software based Kanban systems are available. Ideally to mitigate this Kanban cards should be kept on in-going and outgoing racks.
3. Utilizing the Kanban system results in less opportunity to work ahead of schedule placing performance pressures on staff.
4. It can be inflexible to product mix changes and small or infrequent orders do not fit the model well. It could be argued that the Kanban system is more suitable for medium to large sized organizations.

        

Wathsara Wishwantha Daluwatta