Loading...
Answers
MenuHow to calculate combined velocity if three teams are working on a single story in a project.
Front end, Middleware and Backend three teams are working on a project. Each story touches all three teams. How to calculate a combined velocity of the teams so we can predict the delivery of some features.
Answers
In order to calculate combined velocity, you need to know the total amount of time that each team is spending on the story, as well as how much work they are producing per hour. Then, you can divide this number by the number of hours in a day, and multiply this figure by 100 to get your combined velocity.
Hopefully the Story is divided into multiple demonstrable Outputs and then to specific Tasks/Features. If this is the case, then based on the worklog done & completion achieved on the specific Task/Features by the assigned team-member, his/her velocity could be calculated from these. Hence grouping all the team members outputs completion (tasks/features), Team’s velocity could be calculated i.e., numbers of work/task/features completed in a sprint/milestone/release.
Thanks
Sandeep
Related Questions
-
Which framework would help us to improve our product development: Scum, or Kanban or Scrumban?
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 KanbanPK
-
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 are some good resources to learn about and implement scrum development for business development?
I hold scrum meetings with my developers and tech team every day, so I think a good agile software and a disciplined project manager are probably the best source for scrum and learning about it. There is nothing like a good project manager to act as a scrum master, but one experienced specifically in scrum itself. I have personally utilized YouTube as a good source for scrum meetings, but do not forget that Agile is also the counterpart to scrum meetings. If you'd like to speak about this in more depth, I'd be more than happy to work with you and show you what scrum resources have worked for me. BruceBC
-
What is the best project management tool for a startup developing and scaling a mobile application?
I tried Basecamp, Jira, Unfuddle, Trello and PivotalTracker before for different projects which were developed with agile approach. All of them worked fine to me and I needed some time to setup my framework and processes there. I think it would be worth checking Trello or PivotalTracker which I personally like more than Basecamp because of better agile oriented structure.DL
-
What is the best way to help people estimate their required effort on tasks accurately so the rest of the team can make realistic and accurate plans?
Four thoughts. First, define what maximum and minimum effort estimate is acceptable - for example, tasks should not take less than 2 hours or more than 4. Second, communicate that contingency shouldn't be included in the estimates so they aren't padded. Instead, have some room in the overall plan for tasks to slip. Third, measure actual vs. estimates to learn how the team estimates - you'll find that some people consistently over estimate, and some consistently under estimate. Show them and have them adjust course. Finally, make sure that the people estimating understand that no answer is acceptable - it is better to redirect a task than have wide guesses.JD
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.