Tag Info

Hot answers tagged

6

Should we really be trying to estimate to the work-hours level of precision at this point? Hell no, but it happens all the time. Partly it's because most places do SortaAgile. SortaAgile doesn't believe in story points. It doesn't believe that individuals have different velocities. And it certainly doesn't believe in team involvement. Partly it's ...


2

It doesn't sounds like you're doing any kind of methodology that I'm familiar with. You wouldnt normally have tasks in a backlog. How do you prioritize a task? You can't complete a story without implementing all tasks so it makes no sense to have them in the backlog. Stories should follow INVEST Should we really be trying to estimate to the work-hours ...


2

It sounds like you're thinking about what a project is differently to how most of this kind of software does. As a result, you're also breaking down other pieces differently. In a tool like Jira: A project is an entire piece of software - a product. So in your case, you have one project. Modules within a piece of software are called components. In your ...


1

I would recommend having your development team try to take on the role of user acceptance testing, at least to the extent possible. It may not be as effective as the actual users, at least until the developers have a strong understanding of the domain and how the users carry out their work in the software, but it will help catch the big things before you get ...


1

People over process. That's one of the core tenants of Agile, if a process isn't working for your team, scrap it or modify it. Let the team modify it to fit their needs.



Only top voted, non community-wiki answers of a minimum length are eligible