Loading...
Answers
MenuWhich framework would help us to improve our product development: Scum, or Kanban or Scrumban?
Answers
If your team is releasing updates constantly & there are edits to the list of features to do, Kanban would be the way to go.
AGILE is best when everything is defined and would not change.
I work in a company that worked on AGILE. But the nature of our team's work would constantly have numerous changes by the client mid-sprint. So, we shifted to Kanban
I have built a number of high-performing teams and defined the respective processes.
Honestly, I don’t think you are asking the right question. Asking for the simple red or the blue pill may be tempting, but it will not get you the results you need. For Scrum or Kanban to work out of the textbook, certain assumptions need to be met (which is rarely the case).
So in order to really improve your situation, you need to
- start with your customers, and understand how you serve them. What is important? What makes their day, and how do you make an impact?
- where is your risk? Is it with developing the wrong product? Or with being too slow/too late?
- do you have stable requirements, or would you need to adjust rather quickly?
And there is more depending on how you operate, or want to operate in order to succeed.
The right process for you needs to be derived from this, and then iteratively refined.
Sorry, this is more work than you looked for, but it will save you a lot of headache trying to make a blueprint work that never fitted in the first place.
Don’t bet your company on a method - shape your processes according to your situation. Get help to get it right.
Process evolution at startup is always a challenge.
Your current team (one developer and 2 advisors) is in actual one member team ( I am assuming that advisors are not doing any technical software development)
Formal SDLC approach will be a challenge and it will always be for this software developer to juggle
a) New feature / functionality development
b) Defect resolution from past year release
c) Any incident , defect or change in the past year release
My suggestion would be to build an ServiceDesk like item log ( divided into three categories above) and prioritize for the developer in consultation with manager and technical advisor.
To understand which one among these three is good for you, you must look at the differences they will make to your product. Let me consider the difference from all aspects, so that you can make a better judgment.
1. Roles and Responsibilities.
Kanban: There are no pre-defined roles for a team. Although there may still be a Project Manager, the team is encouraged to collaborate and chip in when any one person becomes overwhelmed.
Scrum: Each team member has a predefined role, where the Scrum master dictates timelines, Product owner defines goals and objectives, and team members execute the work
2. Due Dates / Delivery Timelines.
Kanban: Products and processes are delivered continuously on an as-needed basis (with due dates determined by the business as needed).
Scrum: Deliverables are determined by sprints or set periods of time in which a set of work must be completed and ready for review.
3. Delegation & Prioritization.
Kanban: Uses a “pull system,” or a systematic workflow that allows team members to only “pull” new tasks once the previous task is complete.
Scrum: Also uses a “pull system” however an entire batch is pulled for each iteration.
4. Modifications / Changes.
Kanban: Allows for changes to be made to a project mid-stream, allowing for iterations and continuous improvement prior to the completion of a project.
Scrum: Changes during the sprint are strongly discouraged.
5. Measurement of Productivity:
Kanban: Measures production using “cycle time,” or the amount of time it takes to complete one full piece of a project from beginning to end.
Scrum: Measures production using velocity through sprints. Each sprint is laid out back-to-back and/or concurrently so that each additional sprint relies on the success of the one before it.
6. Best Applications.
Kanban: Best for projects with widely varying priorities.
Scrum: Best for teams with stable priorities that may not change as much over time.
This is the difference primarily between Kanban & Scrum, now we will investigate the difference between Scum, Kanban and Scrumban
1. Scrum: Scrum is one of the dominant Agile frameworks which has a set of guidelines that manage the development of product. Methodology is iterative, measurable and incremental, since it focuses on really tightening up development cycles, which are based on scope that is divided into smaller tasks amounts of effort called sprints, rather than extensive planning, building, testing or deployment.
Advantages:
I. Iterative and incremental method allows tracking of a project workflow and provides intermediate results.
II. Adaptability for product development: scrum allows you to change priorities and requirements. Also, add modifications or features quickly.
III. Participation and enhancing communication: all team members are involved into process and motivated to express their opinion and contribute to all decisions. Team can easily communicate and eliminate obstacles as soon as possible.
IV. Cooperation: enhanced customer and client relationships by daily communication.
V. Increasing productivity: it allows to deliver products more quickly by determining an estimation and comparing the performance of team productivity.
Disadvantages:
I. Requires experienced team: usually, scrum methodology is applied for small 5-8 people teams. Team members must be committed to the project, as this framework requires experienced team. If a team consists of novices in this area, there might be a risk of not to completing the project on time. Moreover, strict control over the team might put a lot of pressure on them which may also lead to failure.
II. Time expenses: after each sprint, a new sprint planning needs to be done, which may consume a lot of time if a longer sprint is planned. Unexpected issues may also hinder the process of completing a sprint on time, thus more time will be needed to remove those issues.
III. Scope creep: scrum does not have a defined end date. For this reason, a released work may not have everything that the stakeholders want, and new features are needed to be released.
IV. Iteration definition: the scrum estimation is one of the hardest and wasteful parts, as tasks must be well defined, otherwise estimated project costs and time will not be precise.
Kanban: Kanban is a Lean scheduling manufacture system developed in Japan. A Kanban system utilizes visual cues that calculate what to produce, when to produce and how much to produce. Kanban is intended to manage the workflow and increase performance which aims are to focus the efforts on the items that bring value to the end customer and remove waste.
Advantages:
I. Reduces waste and scrap: products are manufactured only then when they are needed. In this way overproduction is eliminated.
II. Inventory level management: Kanban has great inventory practices which smoothens out inventory levels and eliminates carrying costs.
III. Flexibility in production: Kanban ensures you are not stuck with excess inventory if there is a sudden drop in demand for a product.
IV. Increases productivity and efficiency: Kanban helps to eliminate the time waste and people can focus on current work. For this reason, making supplies is more accessible and productivity increases.
Disadvantages:
I. Less effective in shared-resource situations: suppose that upward production line is made of several parts. Downstream line requires make more parts, but it requires a buffer to ensure that downstream station does not run out. System becomes more complex because each part needs a separate signalling card.
II. Inflexible in demand changes and product mix: Kanban system assumes there is a stable production plan, where supplier always delivers components for production when it is needed. Therefore, the system is not suitable for industries where volumes and mixes of production fluctuate.
III. Variability elimination: system can be disrupted by unpredictable and lengthy down times and any variability may affect system’s functions.
IV. Production flow: because Kanban requires planned weekly and monthly schedules linked with day-to-day flexibility, it may not be possible in an environment where multiple or short length product types are manufactured.
Scrumban: Scrumban is a mixed methodology of both Scrum and Kanban which increases adaptability and universality for product manufacturing and support focused companies.
Advantages:
I. Saving time: Scrumban uses planning on demand technique so there is no need to do estimating or sprint planning. Team plans only when there is a demand. For this reason, team members get extra day of work.
II. Quality: saved time on planning allows to focus on quality control and to verify if work item is ill-formed. Saved time allows to control a manufacturing process and to inspect if work is promoted to the ready queue. If something ill-formed is found, then it gets bounced and troubles are eliminated, then process is repeated once again.
III. Waste minimization: Scrumban uses inter-process buffers and flow diagrams to show weaknesses and opportunities of the process. This gives an opportunity to eliminate everything that is not adding value to the customer.
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
What would be a good approach for marketing a software development businesses?
For software development business LinkedIn ads, content marketing and Google Adwords don't work well. The best and most cost effective method is email outreach. Try to find the contacts of key decision makers in Bay Area from your target companies. You want to present yourselves as custom mobile and web development specialists and highlight your core competencies to get an initial call to discuss their mobile strategy or software development needs. Attaching your case studies how you helped other similar businesses and your portfolio can be extremely helpful as well. Try to always focus on the benefits in you pitch that they can get by working with you and point their missed opportunities of not having certain types of software or apps for their business. Clients love that software development companies have not only strong execution but also ideation skills. Hope this helps. If you have any questions I am also available on call for your convenience.AA
-
How should the dynamic between a ux designer and a developer who are working together look like?
It depends a lot of in the skill sets and experience of both people but in most cases the ux designer should be controlling the developer pretty heavily in order to make sure his ideas come through properly. The UX designer may just need to work on his approach so people don't feel bossed around and more like they are working together. In an ideal world, there would be a project manager who makes sure everything is communicated well and keeps the dynamic feeling great.JM
-
Which is the best hosted free bug tracking tool for a team size of up to 10 members?
Being a freelance developer for the last 10 years or so, I have seen and used almost every project management software you can think of, open-source and closed, and I have found that the "best bug tracking tool" completely depends on your process. I employ and direct teams in an Agile process that involves loose story-based requirements with point-based estimates, two-week cycles of iterative development, planning and retrospective sessions, and look-ahead and show-and-tell meetings with the stakeholders. It's important to me, then, that my tools have a method of capturing all those pieces with as much detail as I need but no more. On projects, I've successfully used Pivotal Tracker, Unfuddle, Redmine, Codebase HQ, Basecamp, Trello, and many others. I usually recommend people to Trello for light, agile management; it's essentially a digitized version of sticky notes and swim lanes. If your team actually needs a full-featured ticketing system, see Redmine (Rails), Trac (Python), or Mantis (PHP), depending on your language preference. Hosting a version of these yourself is fairly trivial, and numerous options exist for cheap or free hosted versions. For something in the middle, Github Issues is a good fit and the open-source clone GitLab.org replicates most of those features nicely. However, if you're looking for a hosted version, you're probably looking to offload that tricky "backup" thingy, and in that case, how important is your data? How proprietary? What's your business model? If you're working on an open-source project, Github will give your team a free account with private repos, issues, wikis, and the like. If you're okay with your project being "readable by all", public projects on Pivotal are still free. I'm mostly a consultant these days, leading small groups of junior or intermediate developers into a more productive, more mature, fully operational teams of senior software developers. One of the first things I teach folks is how to use a project management system... and why! It'll save your bacon if it's simple, effective, and reliable. With a few minutes of discussion about your project, I can probably help you select the right tool and service for your team. Let me know if I can help with that. Best of luck!DR
-
What's the best way to build a MVP web app that handles order management, purchasing, invoicing, supplier management and inventory?
The best way to build an MVP for any SaaS product is to create a landing page that looks like a real product. Here's an example of one I built. http://www.happiily.com In this case, it advertises the primary features of the product and invites people to sign-up. When they do, they are asked for information which qualifies the person and then sends me an email. I built this quickly and very inexpensively and started getting inbound leads from it shortly thereafter. I got on the phone with each person who signed-up and explained the features I wanted to build and was able to do a lot of customer learning based on that. Happy to talk to you in a call if you'd like to talk more about customer development with SaaS products.TW
-
How do I run a closed beta test for my mobile application? Development will be finished in 3 weeks.
You should try to engage people using social networks, it is easier to spread than email. The conversion rate on emails are low but is still a valid tool for that. Send and email with a simple and objective message that will make people want to try. The best way to have feedback from users is to watch them use the app. You should put them on the hands of everybody that you can and without any instrucions and just watch, don´t even say that the app is yours. Try to do it a lot. If you want feedback from others, you can include the feedback form inside the app and suggest users to answer occasionally. I would also strongly recommend to use a tool as Flurry Analytics. Is the best way to get data from how is the use of the application. Pay attention to those data and be open to change your app a lot, you may need more features or cut some off to make it easier to use. If you need more help please contact me.BS
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.