Skip to main content

Hello Agilists.  My team is evaluating the Agile Accelerator tool to see if it will meet our needs for managing projects.  Looking for some best practices, suggestions, answers to some items.  Appreciate the help.

 

  1. Can we get around the 31 day requirement for a sprint?  Can that be changed or is that baked into the App Exchange package?

  2. Recommendation needed.  We want to keep this simple so the tool can work for every type of project.  We aren't iterating on the same product each month.  We have many types of projects in flight.  I'd prefer to have a project level (Release?), stories, then work underneath.  I see that Agile Accelerator use Sprints as its main master level.  If that's the case, we could have the sprint dates match the release dates for simplicity (except for the issue in #1).

  3. Does anyone use the "actual hours" field?  I notice it isn't a formula field.  Instead the automation is around hours remaining only.

1 comment
  1. Feb 22, 2017, 9:58 AM

    Hello,

    1) dont know, and wouldnt suggest it in a Scrum Context

    2) AA supports Scrum and Kanban - it might be that Kanban (one team per project e.g.) suits you better

    3) Ive asked that some time ago, you'd need to build your own implementation

0/9000