Skip to main content
14 events
when toggle format what by license comment
May 30, 2017 at 22:49 answer added Erik Nguyen timeline score: 1
Apr 5, 2017 at 20:16 comment added JeffO Agile likes traditional software development so much, it does it over and over again.
Apr 5, 2017 at 10:46 vote accept Andre Borges
Mar 29, 2017 at 17:11 answer added Niels van Reijmersdal timeline score: 0
Mar 29, 2017 at 15:58 answer added JacquesB timeline score: 11
Mar 29, 2017 at 15:44 answer added Peter timeline score: 0
Mar 29, 2017 at 14:07 comment added Nathan Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team" - Scrum Guide. Your example contains neither self-organising nor self-reliant teams. It's pretty obviously not Scrum.
Mar 29, 2017 at 13:57 comment added Blrfl No approach will ever be agile enough to be considered "fully agile," whatever that is.
Mar 29, 2017 at 13:43 answer added JeffO timeline score: 2
Mar 29, 2017 at 12:35 history edited Andre Borges CC BY-SA 3.0
added 240 characters in body
Mar 29, 2017 at 12:32 comment added Andre Borges @BartvanIngenSchenau, I edited the question to clarify these points
Mar 29, 2017 at 12:29 history edited Andre Borges CC BY-SA 3.0
added 240 characters in body
Mar 29, 2017 at 12:17 comment added Bart van Ingen Schenau There are some important aspects missing in your process description: 1. How often does marketing get to see what their feature is starting to look like? 2. What happens if Marketing doesn't like the direction that the product is taking and wants to make changes to the feature halfway through?
Mar 29, 2017 at 8:56 history asked Andre Borges CC BY-SA 3.0