I think Kanban alone is not sufficient for software development . It can be useful for bug fixing iterations , but the main development will get more benefit from Scrum.
Please share your thoughts on this. Saving Changes...
Gianpaolo CervoManager| BASF Italia SpaCesano Maderno, Italy, Italy
Hi Vinod,
I agree with your comment.
In my experience I also see Kanban alone not enough. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Kanbam, Scrum, DSDM, nothing is enough to develop software by itself. No matter you will use you have to take into account this: think about a pyramid. Suposse the pyramid has 5 floors. The basement is quality. With basement in quality you will have one floor over "models" (adaptative, predictive). Over the models you have methods (SCRUM, DSDM, SDLC, etc). Over the metods you have tools. All this stuff will be components of your life cycle. With that on hand you have to start an analysis about your current organizational situation to determine what best fits to your initiative. Saving Changes...
I have seen situations where Kanban is sufficient. In one such case, it was the conversion of a large group of reports from one software package to another. The Backlog was easily managed by the user community based on their needs, and the availability of their staff to validate the converted reports written in the new software. Note that this was a "conversion in place" ; the requirements were fixed - no new features.
...
1 reply by Vinod Vadakkethalakkal
Nov 04, 2016 12:57 PM
Vinod Vadakkethalakkal
...
Thanks, john. What @segio said is correct "you have to start an analysis of your current organizational situation to determine what best fits your initiative."
I have seen situations where Kanban is sufficient. In one such case, it was the conversion of a large group of reports from one software package to another. The Backlog was easily managed by the user community based on their needs, and the availability of their staff to validate the converted reports written in the new software. Note that this was a "conversion in place" ; the requirements were fixed - no new features.
Thanks, john. What @segio said is correct "you have to start an analysis of your current organizational situation to determine what best fits your initiative." Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
@Vinod, would you care to provide any reasoning behind your statement?
I have worked with a large number of both Kanban and Scrum teams and really seen no difference in terms of type of work addressed nor the frequency of delivery. The two methods are merely alternate means to limit the work in progress.
The one difference, from the technical side, is that a Scrum time box provides a clear stopping point fro a delivery. In Kanban, teams often need a stronger configuration management approach to allow delivery without leakage of in-process work. Saving Changes...
Anonymous
As a software development methodology SCRUM is well defined and also have self explained tools and techniques and knowledge ares etc. brundown chart ,relative prioritization(T&T and KA's are not relevant in agile exams) . Where as KANBAN is a signal system that shows throughput of a process by identifying bottlenecks. It can be used with any exisitng process to help reduce costs and increase efficiency.
I didnt get an opporutinity to work on pure KANBAN teams , Many of the smaller organizations in india using a hybrid model of SCRUM + KANBAN boards ( Scrumban ?? ) Saving Changes...
Anonymous
Nov 19, 2016 6:55 AM
Replying to Wayne Mack
...
@Vinod, would you care to provide any reasoning behind your statement?
I have worked with a large number of both Kanban and Scrum teams and really seen no difference in terms of type of work addressed nor the frequency of delivery. The two methods are merely alternate means to limit the work in progress.
The one difference, from the technical side, is that a Scrum time box provides a clear stopping point fro a delivery. In Kanban, teams often need a stronger configuration management approach to allow delivery without leakage of in-process work.
Thanks wayne . As a software development methodology SCRUM is well defined and also have self explained tools and techniques and knowledge ares etc. brundown chart ,relative prioritization(T&T and KA's are not relevant in agile exams) . Where as KANBAN is a signal system that shows throughput of a process by identifying bottlenecks. It can be used with any exisitng process to help reduce costs and increase efficiency.
I didnt get an opporutinity to work on pure KANBAN teams , Many of the smaller organizations in india using a hybrid model of SCRUM + KANBAN boards ( Scrumban ??) Saving Changes...
Thanks, Wayne . As a software development methodology, SCRUM is well defined and also have self-explained tools and techniques and knowledge area etc. burndown chart ,relative prioritization(T&T and KA's are not relevant in agile exams) . Where is KANBAN a signal system that shows throughput of a process by identifying bottlenecks? It can be used with any existing process to help reduce costs and increase efficiency.
I didn't get an opportunity to work with pure KANBAN teams , Many of the smaller organizations in India using a hybrid model of SCRUM + KANBAN boards ( Scrumban ??) Saving Changes...
