Exactly. We've had several projects that were canceled within the first few sprints. The development team kept finding contradictions in the requirements, such that the requirements couldn't be implemented
without breaking some other critical aspect of the system.
From a business standpoint, one might consider the projects a failure. However, Scrum did it's job quite well, and prevented us from spending
months working on something that simply couldn't be delivered.
Same here. The fact that we aborted sprint 2 was probably the one of the best things we've done so far in our project. It sent a clear message that we can't, and thus won't, work on a project that is doomed to fail. The message was received loud and clear, things have shaped up considerably since then, and we're back on track. Not perfect, but probably as good as the organization will allow right now.
Your message has been successfully submitted and would be delivered to recipients shortly.
Changes have not been saved
Press OK to abandon changes or Cancel to continue editing
Your browser is not supported
Kindly note that Groups does not support 7.0 or earlier versions of Internet Explorer.
We recommend upgrading to the latest Internet Explorer, Google Chrome, or Firefox. If you are using IE 9 or later, make sure you turn off Compatibility View.