24901Re: [scrumdevelopment] Potentially releasable software
- Nov 1, 2007Mark Graybill wrote:
> - Our software is classified by the FDA as a Class II medical device soI wonder how PatientKeeper is doing it.
> getting filing done every 30 days is a challenge.
> - Our full testing suite takes a full week.What are you planning to do to decrease this time?
> - From a project standpoint, 30 day Sprints are challenging and 15 dayWhat are the roadblocks to getting a releasable product in that time frame?
> Sprints impose a near impossibility to produce a releasable product or
> even potentially releasable at the end of every Sprint.
> - The idea of deploying at this frequency has not been well received byThat probably means that receiving a deployment is in some way "painful"
> our customers.
to your customers. Where is that pain coming from, and how could you
mitigate it? What would be needed to make it a no-brainer?
> The proposal in debate is this:I always thought that was the *definition* of a user story. Isn't it?
> - Each user story involves a procedure to bring it to potentially
> releasable status.
> - The end result is a feature tested and integrated into the product.Sure. "Done done".
> - But the product itself does not go through full testing every Sprint.If you don't fully test the product, how do you never whether you are
> - Have alpha releases that only require an alpha contract and do thatWhat does "alpha contract" mean in this context, and how would it help?
> every two Sprints.
- << Previous post in topic Next post in topic >>