B-a-Analyst

What is Kanban? Kanban is an Agile way of development just like Scrum being one. The main idea behind the Kanban system is to deliver what the process needs exactly when it needs it .The goal of Kanban is to identify potential bottlenecks in your process and fix them so work can flow through it cost-effectively at an optimal speed or throughput. The mantra is “Fail fast! Fail often!” As stated on Wikipedia Kanban(signboard or billboard in Japanese) is a scheduling system for lean manufacturing and just-in-time manufacturing (JIT). Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency. Kanban is one method to achieve JIT. While kanban was introduced by Taiichi Ohno in the manufacturing industry, it is David J. Anderson who was the first to apply the concept to IT, Software development and knowledge work in general in the year 2004. The four foundational principles and six Core Practices of the Kanban Methodology are provided below:

Q. What is Scrum ? A: Scrum is an Agile approach of software development where software development is released in iterations (Incremental approach) and at the end complete product is delivered where customer needs are met unlike traditional waterfall approach where requirements can't be updated / modified during development cycle. There are various methods to track project status. Scrum uses BurnDown and BurnUp charts to track progress and demonstrate change using graphs.This helps in project forecasting as well. BurnDown Chart: A burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal. That is, it is a run chart of outstanding work. It is useful for predicting when all of the work will be completed. Progress on a Scrum project can be tracked by means of a release burndown chart. The ScrumMaster should update the release burndown chart at the end of each s

What is Product Backlog ? Product Backlog is a collection of list of items to be developed i.e. It is the list of functional and non-functional requirements ordered based upon the priority of requirement. In other words Product Backlog is simply a list of all things that needs to be done within the project. It replaces the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories. As per SCRUM, The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog