project plan preparation based on Agile development

Agile Estimating Governance Information Technology Schedule Management Scheduling Work Breakdown Structures (WBS)

Robert Poddar Project Manager| Identiv Private Limited Chennai, Tamil Nadu, India

Hi,

I am preparing a Gantt chart project plan for a pure Agile based Software development. I am confused as to how should i go about preparing the plan and tracking the same. How do you also do resource levelling, since in my case, we have a single team that are working on 2-3 product releases that should go to market at the same time.

Note:
1. Currently, we are not doing a backlog scrub of all tickets that are supposed to be in the release. Upfront we will not know how many points will it take to complete the release.
2. When the PO indicates that a particular ticket needs to be part of the release, the respective Tech Lead will go and update the estimate effort of the JIRA ticket. The ticket is added into the current active Sprint. If it doesn't get done in the current Sprint, then it will automatically move to the next Sprint, when the current Sprint is closed.

thanks
Robert.

Posted: Jul 27, 2018 5:26 AM

Sort By:

< 1 2 3 >

Robert Poddar Project Manager| Identiv Private Limited Chennai, Tamil Nadu, India

Oct 24, 2018 2:56 PM

Replying to Kavitha Koraboina

...

Hello Robert,

I agree with what other contributors have already mentioned. However, found online that MS Project has a version which has features usable for an Agile project, I have not used it myself so not very sure.

Regards,
Kavitha.

Hi Kavitha,

Thanks. I am using Smartsheet project scheduling tool. It is a cloud based tool. I will check a trial version of MS project and see how the Agile feature works in MS Project.

thanks
Robert.

Posted: Oct 29, 2018 7:57 AM

Robert Poddar Project Manager| Identiv Private Limited Chennai, Tamil Nadu, India

Oct 24, 2018 8:38 PM

Replying to Lenka Pincot

...

Hi Robert, do you have a roadmap for the product you are supposed to develop? Product roadmap shows major features, you may phase them in time, but you will not run into conflict when scheduling more detailed user stories as you progress with your iteration planning. If that’s a product you are creating, such roadmap should be available in a rough time perspective. But then for individual sprints you use the backlog of user stories and assign them to iterations based on priorities. Would it help?

Hi Lenka,

Yes we do have a product roadmap, in the sense that our software needs to support a particular hardware product.
Currently, what we are doing is having the software requirements entered in JIRA. Each component team creates the JIRA ticket related to the requirement and sizes the ticket.

I pull the JIRA tickets that are meant for the release and add up all the efforts entered by the team and then through calculation come up with a rough effort in man months to complete all the requirements.

In my project plan, i will have all the tickets having the same start & finish, since the team can take up any ticket. I factor some time for bug fixes and then come up with a release date. I baseline the plan and track the same using this baseline release date. Not sure if this is the right way, but it is helping to some extent.

thanks
Robert.

Posted: Oct 29, 2018 8:03 AM

< 1 2 3 >

Please login or join to reply

project plan preparation based on Agile development

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters