I have continued to do some digging and although there are many scrum
oriented plugins I have come to the same conclusion for each: they don't
meet up to how we work. After some thought, design and prototyping I
started hacking on a plugin geared towards the way we are tending to work
as developers. If anyone is aware of a plugin that already does what I
describe below, please let me know as I have been unable to find anything
close. Before I went much further, I thought I would present my idea for
feedback. The assumptions I am making:
Projects in Redmine represent a code base. Each code base has it's own
release cycle and issues.
Feature work is trending towards being a small team making changes
across multiple projects.
Redmine trackers are not an efficient way to manage issues for a feature
team
Goals
Feature teams need any easy way to manage all of the issues across
projects
Feature teams need to be able to create a backlog of issues
Feature teams need to represent a sprint and manage issues for that
sprint
The community should be able to see an overview of current teams and
their progress
General Design
The general design I have come up with is to create a plugin
(redmine_teams) that allows the creation and management of a team.
One or more Redmine users can be assigned to a team to manage it.
Teams can be created and a backlog is automatically generated for that
team
Teams can create sprints that can be loaded up with issues from projects
Issues belong to teams, and can only belong to a single team
Issues that belong to a team must belong to a teams backlog or a sprint
Questions
Q) Couldn't we just create a project per team?
A) We could, however, projects involve managing a set of issues ear marked
against the project or subprojects towards the goal of creating releases.
Feature teams desire to manage issues already marked against project(s)
that become part of the releases for those individual projects. There
wouldn't be a way to know that issue #345 targets the Foreman core project
but is part of the Rails 4.x team's work load. Projects could be the
answer with a derivative of the current Redmine project setup with the
ability to cross assign issues to "code projects" and "team projects".
Q) What can the plugin do at the time of this writing?
A) Teams can be created and issues can be assigned to a team and sprint on
the issue edit page. The issue details page also shows the current team
information. Team sprints/backlogs show a list of issues for each. See
Feedback would be greatly appreciated as I would like to ensure that:
a) This plugin makes sense and will help teams work more efficiently
b) Fits our needs as a project
c) Meets the needs of Feature teams
sounds good, just one nit. Why do we need to be able to assign an issue to the
team? Would association with team's backlog be enough?
···
--
Marek
On Sunday 31 of May 2015 20:23:11 Eric D Helms wrote:
All,
I have continued to do some digging and although there are many scrum
oriented plugins I have come to the same conclusion for each: they don’t
meet up to how we work. After some thought, design and prototyping I
started hacking on a plugin geared towards the way we are tending to work
as developers. If anyone is aware of a plugin that already does what I
describe below, please let me know as I have been unable to find anything
close. Before I went much further, I thought I would present my idea for
feedback. The assumptions I am making:
Projects in Redmine represent a code base. Each code base has it’s own
release cycle and issues.
Feature work is trending towards being a small team making changes
across multiple projects.
Redmine trackers are not an efficient way to manage issues for a feature
team
Goals
Feature teams need any easy way to manage all of the issues across
projects
Feature teams need to be able to create a backlog of issues
Feature teams need to represent a sprint and manage issues for that
sprint
The community should be able to see an overview of current teams and
their progress
General Design
The general design I have come up with is to create a plugin
(redmine_teams) that allows the creation and management of a team.
One or more Redmine users can be assigned to a team to manage it.
Teams can be created and a backlog is automatically generated for that
team
Teams can create sprints that can be loaded up with issues from projects
Issues belong to teams, and can only belong to a single team
Issues that belong to a team must belong to a teams backlog or a sprint
Questions
Q) Couldn’t we just create a project per team?
A) We could, however, projects involve managing a set of issues ear marked
against the project or subprojects towards the goal of creating releases.
Feature teams desire to manage issues already marked against project(s)
that become part of the releases for those individual projects. There
wouldn’t be a way to know that issue #345 targets the Foreman core project
but is part of the Rails 4.x team’s work load. Projects could be the
answer with a derivative of the current Redmine project setup with the
ability to cross assign issues to “code projects” and “team projects”.
Q) What can the plugin do at the time of this writing?
A) Teams can be created and issues can be assigned to a team and sprint on
the issue edit page. The issue details page also shows the current team
information. Team sprints/backlogs show a list of issues for each. See https://github.com/ehelms/redmine_teams
Feedback would be greatly appreciated as I would like to ensure that:
a) This plugin makes sense and will help teams work more efficiently
b) Fits our needs as a project
c) Meets the needs of Feature teams
···
On Mon, Jun 1, 2015 at 2:53 AM, Marek Hulan wrote:
Hello,
sounds good, just one nit. Why do we need to be able to assign an issue to
the
team? Would association with team’s backlog be enough?
–
Marek
On Sunday 31 of May 2015 20:23:11 Eric D Helms wrote:
All,
I have continued to do some digging and although there are many scrum
oriented plugins I have come to the same conclusion for each: they don’t
meet up to how we work. After some thought, design and prototyping I
started hacking on a plugin geared towards the way we are tending to work
as developers. If anyone is aware of a plugin that already does what I
describe below, please let me know as I have been unable to find anything
close. Before I went much further, I thought I would present my idea for
feedback. The assumptions I am making:
Projects in Redmine represent a code base. Each code base has it’s own
release cycle and issues.
Feature work is trending towards being a small team making changes
across multiple projects.
Redmine trackers are not an efficient way to manage issues for a
feature
team
Goals
Feature teams need any easy way to manage all of the issues across
projects
Feature teams need to be able to create a backlog of issues
Feature teams need to represent a sprint and manage issues for that
sprint
The community should be able to see an overview of current teams and
their progress
General Design
The general design I have come up with is to create a plugin
(redmine_teams) that allows the creation and management of a team.
One or more Redmine users can be assigned to a team to manage it.
Teams can be created and a backlog is automatically generated for that
team
Teams can create sprints that can be loaded up with issues from
projects
Issues belong to teams, and can only belong to a single team
Issues that belong to a team must belong to a teams backlog or a
sprint
Questions
Q) Couldn’t we just create a project per team?
A) We could, however, projects involve managing a set of issues ear
marked
against the project or subprojects towards the goal of creating releases.
Feature teams desire to manage issues already marked against project(s)
that become part of the releases for those individual projects. There
wouldn’t be a way to know that issue #345 targets the Foreman core
project
but is part of the Rails 4.x team’s work load. Projects could be the
answer with a derivative of the current Redmine project setup with the
ability to cross assign issues to “code projects” and “team projects”.
Q) What can the plugin do at the time of this writing?
A) Teams can be created and issues can be assigned to a team and sprint
on
the issue edit page. The issue details page also shows the current team
information. Team sprints/backlogs show a list of issues for each. See https://github.com/ehelms/redmine_teams
Feedback would be greatly appreciated as I would like to ensure that:
a) This plugin makes sense and will help teams work more efficiently
b) Fits our needs as a project
c) Meets the needs of Feature teams
