Do your stories include tasks across disciplines? How do you do capacity planning?
My organization does web projects and employs a handful of disciplines like backend dev, frontend, BA, UX, graphic design, QA. We’ve been pushing to have tasks for every discipline in our sprints with explicit dependencies (Can’t build a page without comps, can’t do comps without wires, etc). I’ve heard some other organizations say that scrum is only for dev tasks. Are we barking up the wrong tree? And, if not, are there any good tools for doing capacity planning when only certain resources can do certain tasks?
How to time the sprints in Scrum to allocate time for TDD?
We have sprints of 4 weeks duration. What I have been doing is 3 weeks dev time and 1 week of pure manual/automated testing, stabilization and shipment assurance testing.
Where to put details about the acceptance criteria of a user story?
In this blog post about acceptance criteria the author explains that good acceptance criteria should:
Task Planning on an Agile Team
At the beginning of each sprint our team will pull in a handful of user stories and then, one by one, write slightly more detailed tasks for them as well as assign specific hours to each task.
Scrum: Short VS long sprint
We were trying to figure out the optimal sprint length for our project. After working on a 3-weeks basis we thought that cutting the sprint to 2-weeks would provide better velocity.
Functional metrics in Agile methodologies
I’m preparing a presentation about Agile methodology for managers (not programmers) and I’m looking that, from a side, the Agile talks about functional perspective*^ (in Scrum we have planning game) but, from other side, it lacks any (standard) definition of **functional measure.
Keeping agile with zero-bug/defect policy
In our project we work in a zero-bug (a.k.a zero-defect) methodology. The basic idea is that bugs are always higher in priority than features. If you’re working on a story and it has a bug it must be resolved in order for the story to get accepted. If a bug is found during the sprint for an older story we need to put it next on our backlog and resolve it – top priority.
Is it possible to shuffle team in between a sprint?
We are working on scrum framework. Now a situation arise that we have to shuffle 2-3 scrum team members in between sprints.
Agile MVP (Most Valuable Player/Programmer)
Recently I’ve been involved in an agile project (using scrum) where management came up with the idea that the team would nominate a developer ‘MVP’ as well as a QA ‘MVP’ at the end of each sprint, voted on by the team. The MVP then gets a small monetary reward and free lunch as well as a trophy to display on his desk. We’ve had two sprints so far with this reward system in place.
Daily Scrum when the team is just fixing bugs
I understand all the advantages of Daily Scrum and my team does it when we are working on stories.