Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

An active sprint is a sprint which has been started and is now visible in Work mode.

 

See also future sprint.

 

  • No labels

5 Comments

  1. grant luna

    A couple of questions about the new (5.9.x) Scrum Rapid Board ...

    *Can I have several active sprints within a project?

    *Can I display several active sprints on multiple projects on one Scrum Rapid Board?

    Basically, I have many overlapping active sprints across many different projects/products and I would like to have one master board. I currently use the Kanban board for this and get decent results. However, I like the new features within the Scrum Rapid Board.

  2. Johnny

    I am evaluating 5.10.1, and it appears to allow still only one active sprint per Rapid Board.  The Sprint custom field is still used by GreenHopper internally only.  Not sure what happens if you have multiple Rapid Boards - I suppose there is some kind of internal Sprint numbering scheme that avoid collisions across Rapid Boards.

    Re: the overlapping sprints, perhaps consider a workaround of synchronizing your sprints.  Since they should likely not be much longer than 2 weeks, sync'ing should not be that big of a problem.  I know of at least one large company going this route. If your sprints are longer than 2 weeks, ask yourself why.

    Another possibility could be to try using Labels representing the joint "sprint" on an absolute timeline.  E.g., year# + week#, like "Sprint 1232" means "year 2012, week 32" (BEWARE: Y2.1K problem! (smile))  Then try filtering your Rapid Board via the Label.

     

  3. Anonymous

    I am struggling with this as well.  The size of our dev team requires overlapping sprints.  This seems to be a weakness in GreenHopper.  I can't build sprints with future dates, I can only go 1 active sprint at a time.  

     

    Unless I have my projects broken up further, i.e. front end, back end, design, I can't get what I need out of it.  It would be helpful to be able to plan out sprints in advance.

  4. Anonymous

    Hey guys, quick thing I've run into that doesn't make much sense to me. After I start a sprint (via rapid board) I am totally fine with having new issues being created and put into the plan backlog, however, I don't see the reason defects are placed there. We run short two week iterations and I get QA defects logged pretty quickly and I can't imagine how someone can plan defects (smile), so shouldn't they just go right into the sprint?

  5. Pedro Carbonell

    Hi!

    Does anybody know if there's a way to create a Dashboard widget that shows all the active sprints, including Sprint End date?

    It would be very helpful in following the methodoly and ending the sprints as planned.

     

    Thanks!



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.