Skip to main content
9 events
when toggle format what by license comment
Jul 26, 2015 at 16:42 history edited ChrisF CC BY-SA 3.0
remove dead linke
Nov 7, 2014 at 2:32 comment added Jono @Giogio, this is an issue with agile in general. Though a goal is to have people over process, in reality Agile becomes religiously followed - which again puts process over people. Personally I think lean does a better job of this than agile, though it does not attempt to enforce a strictly horizontal structure of the team - it does allow developers to choose tasks better. Assuming your team won't change, a kanban board in addition to what you are doing now could make management happy and you happy as well, giving you freedom to choose your stories/tasks.
Jun 27, 2014 at 8:16 comment added Phoshi @Giorgio: Because structured development enables teams to work together without stepping on each other's toes all the time. We just haven't figured out how to do it perfectly yet.
Jun 27, 2014 at 4:56 comment added Giorgio "people over process": Funny, then why impose the SCRUM process instead of letting people use their own? And why all those measures (pair programming, frequent progress reviews) that, in the name of transparency, allow to monitor the work of developers much more closely?
Jan 21, 2014 at 14:54 history edited Tomás CC BY-SA 3.0
Change "scrum but" to "scrum butt" + add link to scrum butt test
Mar 21, 2012 at 23:38 history made wiki Post Made Community Wiki by thegreendroid
Aug 19, 2011 at 11:20 vote accept Saeed Neamati
Aug 16, 2011 at 12:17 comment added StevenV +1 Scrum (as all Agile methodologies) be heavier on conversation than direction. The PO should be describing what the end result needs to be able to accomplish, then engaging the designers and developers on ways to get there.
Aug 16, 2011 at 12:09 history answered Sean McMillan CC BY-SA 3.0