Skip to main content
Project Management

Return to Answer

deleted 13 characters in body
Source Link
Willl
Willl
  • 2.1k
  • 11
  • 29

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context.

We use it in Scrum, where it's helpful for calculating burndown and velocity, but I should emphasize that, for us, it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management. In my opinion, using it for performance management is much more complex than just the measurement of hours/days a person has logged against a particular task.

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context.

We use it in Scrum, where it's helpful for calculating burndown and velocity, but I should emphasize that, for us, it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management. In my opinion, using it for performance management is much more complex than just the measurement of hours/days a person has logged against a particular task.

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context.

We use it in Scrum, where it's helpful for calculating burndown and velocity, but I should emphasize that, for us, it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management. In my opinion, performance management is much more complex than just the measurement of hours/days a person has logged against a particular task.

added a paragraph for readability; fixed some spelling and grammar, including a run-on sentence. Hope I worded what you were trying to say in the 2nd paragraph correctly. If not, feel free to edit further. +1
Source Link
jmort253
jmort253
  • 9.5k
  • 7
  • 42
  • 88

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context. 

We use it in Scrum, where it's helpful for calculating burndown and velocity, but I should emphasiseemphasize that, for us, it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management which, in. In my opinion, using it for performance management is much more complex than just the measurement of hours/days a person has logged against a particular task.

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context. We use it in Scrum, where it's helpful for calculating burndown and velocity but I should emphasise that for us it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management which, in my opinion, is much more complex than just the measurement of hours/days a person has logged against a particular task.

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context. 

We use it in Scrum, where it's helpful for calculating burndown and velocity, but I should emphasize that, for us, it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management. In my opinion, using it for performance management is much more complex than just the measurement of hours/days a person has logged against a particular task.

Source Link
Willl
Willl
  • 2.1k
  • 11
  • 29

You can achieve this using JIRA (which will manage your issues/bugs/backlog) and Greenhopper (which will handle the Kanban side of it). Devs (or PMs) can log work on the issues that they're working on but, as others have mentioned, it might not be quite right in a Kanban context. We use it in Scrum, where it's helpful for calculating burndown and velocity but I should emphasise that for us it's just about helping us to improve our estimation and not overloading our sprints rather than for performance management which, in my opinion, is much more complex than just the measurement of hours/days a person has logged against a particular task.