Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
I am thinking of using JIRA + GreenHopper for my project management.
I have seen that Green Hopper is for making User stories, sprints.
I am not able to find how do i need to add tasks, or how to break user stories in to sub stories.
Do I first need to create project in JIRA and then use Green Hopper or I can use use Green Hopper standalone for project management?
I am thinking of JIRA as issue tracker not project management.
You need a JIRA project created with the GreenHopper template as a base. There you can create different "tickets" (Epics, Stories, Tasks, Defects etc) and follow through with your project by estimating story points, moving them on the SCRUM board and having reports like burndown charts.
JIRA has a standalone installer that installes a full package (Webserver, Database, JIRA, GreenHopper) on your PC for testing. Although maybe a bit slow on a user PC, I highly recommend it to play around with all the features and see them for yourself.
Greenhopper is a pure agile process tool, with the main focus on planning for the sprints, ordering the backlog and tracking the work using the computerized agile boards. We've been trying to use it as a project tracking tool, but it's not really suitable for that.
Also we've been using Jira plugin called Structure to do the work which is more or less similar to the project management - it allows to create overarching items, subitems, tracks process and helps to do a lot of things that are relevant for the status communication part. On splitting up the user stories and creating subtasks etc. I would assume that your problem is creating a view how they are linked together, this is where Structure does help, as it allows the n depth tree structure to be created.
And after spending almost 4 years trying to figure out ways how to make things work, so that the needs of a project manager are satisfied and also the teams and it doesn't deviate too far away from the scrum - conclusion is that neither of them are perfect. Structure messes up the planning process as you have items in a tree and they don't easily correspond to sprints. And Greenhopper does not really let you do meaningful project management, as it does not show the relation between issues.
Atlassian, if I'm not mistaken, has recently launched a really neat tool, called Rapid Boards, which actually combines aspects of these quite nicely, so this is one of the things I recommend to take a look into.
P.S. I am more and more also inclining towards the opinion that post-it (tm) based agile board is really the most suitable thing for planning and paper and pencil are one of the most important tools for a project manager :).
