Quote:
Originally Posted by jds2001
Interested to hear other's experiences [with scrum] as well....
|
I'm not a software developer anymore, and my first experience with scrum was in the past year, as a subject matter expert and minor stakeholder. I agree that scrum seems best linked to "unstructured" problems, either because your customer (or customer base) doesn't know what the best solution is, or there is more time available to experiment and develop a "final" solution provided that interim functionality is developed. From my "stakeholder" view, scrum appears to be a way to keep stakeholders/customers "in the loop" at the sprint level (a few weeks) while insulating them from the (usually daily) scrums. These sorts of problems were more commonly managed with "spiral" development until recently. In a lot of ways, scrum is a formalization and acceleration of spiral where each 6-18 month spiral is replaced by a number of 3-12 week sprints, each of which is much smaller scope. There is just not enough time in an FRC build season for scrum as I have experienced to work properly; you really do need to develop more solid requirements and build all of your base functionality in parallel. Besides, there is very little interaction with "the customer" resulting in less drift in the functional requirements. The GDC publishes a set of rules at the beginning, and only interacts with development teams through the Q&A process. The requirements only change a few percent during the course of build season, and the GDC customer/stakeholder really doesn't care how you solve the problem/meet the challenge. That stated, the derived requirements and technical requirements are subject to a lot of drift as competition progresses.