Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    Yeah. Nice cargo cult agile process you have there, but without the pesky self organising teams. Also sounds like putting this much effort into the backlog isn't very lean. Commented Mar 16, 2015 at 19:56
  • 1
    Agreed with @NathanCooper. What methodology are you supposed to be doing? Were you expert enough in your chosen methodology to customise it? Commented Mar 16, 2015 at 20:27
  • @daveHillier exactly. Also "agile" isn't a particular methodology. Was it meant to be scrum for example? Commented Mar 16, 2015 at 21:02
  • Well it might have been meant to be Scrum. Certainly not XP. I think the best word to sum up our methodology at this point would be "Rally". Commented Mar 16, 2015 at 21:15
  • 1
    The problem is that if you can't estimate, then you can't decide the sprint commitments. At that point command and control management has murdered agile and is wearing its skin as a trophy. The core of agile is trusting good people to get on with it and the involvement and engagement of the team in delivery, not whiteboards, chairless meetings or jargon Commented Mar 16, 2015 at 21:50