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.

8
  • I am not sure I understand what you mean by "more lightweight". Is that like... nothing at all? No process? Or just like some specs, JIRA tasks and individual developer contribution? So please clarify what you mean by that.
    – Schultz9999
    Commented Jan 11, 2011 at 6:10
  • you don't need it. i'm sure scrum works as a model for either larger teams where there are more variables than you can wrap your mind around, or in situations where the manager is not a good natural leader and needs some kind of training video/template to follow. it sounds like you do not fall into either of these categories, so my condolences. another good team bites the bureaucratic dust.
    – leeny
    Commented Jan 11, 2011 at 7:54
  • 4
    By more lightweight I just mean less rigid. I expect developers to plan tasks, to code review, to evaluate what doesn't work, to share what their doing on a semi-regular basis. I don't however feel that these things must be so strict, e.g. plan every other Monday, stand-up every day at this time, retrospective every other Friday, set-length sprints, etc. I feel I already do a lot of what SCRUM encompasses, but without explicit direction, terminology, or agendas.
    – stapo
    Commented Jan 11, 2011 at 15:28
  • Have you had a look at Kanban or Lean techniques and principles? It sounds like you've already got a fairly Agile process in place. Lean could help you improve without restricting your fluid, working processes. Kanban also uses "cadence" rather than a sprint, which means that each meeting can take place with its own rhythm, rather than having to work with all the other meetings in a 2 week cycle.
    – Lunivore
    Commented Jan 15, 2011 at 17:10
  • 2
    You are talking about Scrum but are quoting the Agile Manifesto. Scrum is about defining artifacts, roles, meetings, sprints, measurement etc. You can definitely be Agile without implementing Scrum and for the most part you can do Scrum and not be Agile.
    – Guy Sirton
    Commented Jul 2, 2011 at 22:38