New answers tagged

2

I would keep everything in the same project since you are working on a single web app. You can create multiple boards in Jira (one for reach team) and manage each teams workload through these boards. Speak to your Jira Administrator to design the project. The product architecture sounds like it is layered (front-end, product micro-services, etc). Sounds ...


0

I've been using TFS for 4 months now, so I'm no expert yet. But I think the burndown provided by TFS (as I understand it) does not work well. You first need to store the availabillity of all team members and the amount of time they will be available for the sprint. Then you also need to register the amount of time left per task. To me this seems like a lot ...


3

I've found that Jira projects best equate to products. This enables better use of the functionality around Releases, Components, and test case management (if you integrate that with your Jira instance through a plugin). In your case, you need to decide if your web application is a product or if the different microservices are each a product. I prefer to ...


1

Create different projects Advantages: No need to differentiate issues assigned to different teams. Just the fact they are in a given project tells you which team is dealing with them No issues with the JIRA inbuilt Scrum functionality although you may see some problems with epics (if stories from an epic need to be worked on by more than one team). ...


2

User story best practices by Mike Cohn Here are some user story best practices by Mike Cohn: Write user stories from the perspective of the person who desires the new capability in this format: As a < type of user >, I want < some goal > so that < some reason >. Discussions are more important than whatever text is written. Add detail by splitting ...


2

How to deal with recurring tasks in a sprint? It really depends on what type of work is performed in those recurring tasks. If the work is about fixing bugs for the application, adding new functionality, any kind of product enhancements, or work that creates a product increment and can be a goal for sprints, then it belongs in your sprint and in your ...


3

A common theme in agile methods is about communication, visibility, and transparency in the work that is being done and what the status of that work is, ensuring that the right stakeholders have access to this information. Without knowing all of the details about this work, it seems like the Product Backlog is not the right place for these. The Scrum Guide ...


Top 50 recent answers are included