Agile tools, can't find any that suits my case or I'm wrong somewhere? [closed]

Question

Closed. This question is off-topic. It is not currently accepting answers.

---

Want to improve this question? Update the question so it's on-topic for Software Engineering Stack Exchange.

Closed 5 years ago.

Improve this question

We have huge modules in our project, each module has a bunch of user-stories, each story contains developer tasks. Actually, we take tasks from multiple modules, since we have some core module features and optional.

Each developer task I should review and merge into master.

So, basically it is just project-task-subtask, right? But it doesn't fit our case.

1. Each project has it's own board - we need one board, actually
2. Sub-tasks cannot have status beside completed/not. So, sub-task is completed, but not reviewed, but PM sees it like this part is done and ready to be tested and touched. Waiting for whole user story to be completed isn't acceptable every time.

I know it is not a resource to find apps, but I dunno where I can ask this questions.

Answer 1

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 case, each of the modules would line up 1-to-1 with a component.

• Stories (developer tasks) belong to a project, and can be associated with 1 or more components. Each story has it's own state (open, in progress, done, closed; these are configurable in Jira), and follows a predefined workflow. In your case, a task and a story are equatable.

• A story can be broken down in to sub-tasks. Each sub-task (like a story) has it's own state, following a predefined workflow.

• A backlog is a collection of stories which need working on. In Jira, this is defined by a filter over all stories in the system.

• A scrum board is a team's view on a product backlog, showing which stories from that backlog are being worked on in the current sprint. The scrum board has a swimlane (row) for each story, and a column for each state, with stories and subtasks appearing in the appropriate columns.

• A large internal project within the product is an epic. An epic can have any number of stories in it.

If you were to use a tool like Jira, you would have a single project, with a scrum board and backlog per team. Stories would be associated with the modules, and work on them would follow the normal workflow.

You could easily divide your teams and backlogs along module boundaries by using an appropriate filter when creating a backlog; eg "only those stories associated with this module"