Some of our teams have struggled with not being able to complete the testing hours for stories in a sprint, and thus not reaching DONE for the story. One team has vollied up the idea of doing the development work in one sprint & sizing that then doing the testing in the next and sizing that. This doesn't seem like the best solution, but wanted input on others experiences. We also think the root cause could be that the stories are too big for the 3-week sprint duration. At this time we are not using any automated testing methods, but are working to begin this later this year. Please
These unanswered questions need your expertise!
Recent Q&A Activity
Which is best tool for GUI Testing & Performance testing
Can You guys tell me the current trends /techniques that are followed in the test case Designing
Suggest me some Agile Automation tool anmes please Agile Automation,
Unless I've misunderstood the principle, agile sprints are about layering on features until you arrive at some final release.
But software can become unwieldy complex and choosing the right data structures and class patterns, for the application, is crucial - isn't it?
So, how can you decide on the right data structures and classes and patterns, at the very beginning of the process, if in the first sprint, you are only dealing with a few of the overall application features?
How do you go about planning the delivery for the year when you work with agile projects? I work in a supplier capacity and need to be able to roughly estimate deilvery dates for projects across the year and understand capacity. I'm new to agile as I've been working with waterfall and that does work easily with scheduling across multiple teams for the year. I'd appreciate any advice anyone could give.
Question from recent Agile Meetup with Scott Sehlorst.
Question from recent meetup with Scott Sehlhorst.
Is it possible to implement Lean principles in the ongoing Agile project?