When product owner express the userstories, scrum team asks for clarification for better understanding.What is the order of actions in sprint planning, is it that tasks of particular user story should be entered in in scrum board or acceptance criteria of the user should be defined first and then entering the details of develeopment tasks with the estimates derived? can you help me with this?
Recent Q&A Activity
We are migrating a slew of reports. I'd like to apply agile methodology for this process. I would you recommend I proceed?
Like IdeaBoardz, Skype, Lync TV, what else ?
(e.g. "Drive" by Daniel Pink is one of my favorites.)
Can we really get good insight, while asking certain questions on agility, how it is practiced etc from agile team menmbers.
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
Can You guys tell me the current trends /techniques that are followed in the test case Designing
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.