| > Purists want you to believe that only pure Scrum works Purists would realize that Scrum was defined to be a self reflecting, self improving system. Scrum allows people to alter scrum to meet their needs. > Scrum deliberately asks the team not to look too far ahead This is not true. The product owner can put as much stuff on the backlog as they like and the team should know about it. Scrum does ask the team to not spend a lot of time estimating out stories that are months down the road (so very loose estimates are ok). > Scrum forces that the plan cannot change during the Sprint. This way they know where they stand during the Sprint. This is true but not totally true. Scrum requires the product owner to "stand back" during a sprint. But, at any time, the product owner can declare the sprint un-productive and it restarts. How does the team know they aren't adding value if the product owner can't stop the sprint? > For a game to be "potentially shippable" after every Sprint (as Scrum requires) the certification requirements See above where scrum allows you to alter the "rules" of scrum to meet the needs of the users. Scrum is not written in stone. |