Skip to main content
21 events
when toggle format what by license comment
Oct 27, 2018 at 15:23 comment added RubberDuck There’s a joke I’m very fond of. “If you’re delivering in months & years, Scrum will help you deliver in weeks & months. If you’re delivering in days & weeks, Scrum will help you deliver in weeks & months.”
Oct 24, 2018 at 15:00 history tweeted twitter.com/StackSoftEng/status/1055111882133008385
Oct 24, 2018 at 13:05 answer added jonathangersam timeline score: 0
Feb 10, 2014 at 18:39 comment added user119325 "That's great, but all of it seems like common sense to me. Why did this need codified?" - I feel the same way when I read about design patterns.
Aug 21, 2011 at 13:25 comment added 52d6c6af "That's great, but all of it seems like common sense to me. Why did this need codified?" So many innovations seem obvious after the fact. Commercial software development is a relatively new industry that requires a mindset shift in the managers and business leaders that is ongoing to this day. Why has the shift taken so long? The reasons are manifold. If I had to choose one, it would be "human nature". A well-defined Gannt chart gives a warm feeling of certainty (albeit a deceptive one). Being told that you do not actually know what you want at the outset of a project is tough to swallow.
Aug 9, 2011 at 19:23 answer added Sean McMillan timeline score: 1
Jul 3, 2011 at 4:27 answer added Antonio2011a timeline score: 1
Jul 2, 2011 at 23:10 answer added anon timeline score: 11
Jul 2, 2011 at 22:38 comment added Guy Sirton 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.
Jul 2, 2011 at 19:20 history migrated from stackoverflow.com (revisions)
Jul 1, 2011 at 21:36 answer added anonymous scrum chicken timeline score: 2
Jan 15, 2011 at 17:10 comment added Lunivore 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.
Jan 11, 2011 at 15:28 comment added stapo 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.
Jan 11, 2011 at 9:09 answer added snakehiss timeline score: 0
Jan 11, 2011 at 8:35 answer added slebetman timeline score: 7
Jan 11, 2011 at 7:54 comment added leeny 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.
Jan 11, 2011 at 6:27 answer added Anne Schuessler timeline score: 14
Jan 11, 2011 at 6:10 comment added Schultz9999 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.
Jan 11, 2011 at 6:10 answer added Schultz9999 timeline score: 1
Jan 11, 2011 at 5:30 answer added Pradeep timeline score: 1
Jan 11, 2011 at 5:14 history asked stapo CC BY-SA 2.5