How to write tasks in Jira when using Scrum?
I am going to start a new project using Scrum and Jira and I have some questions regarding how to write proper tasks in Jira.
In good Scrum, when and how should the ideation and story writing occur? [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. It seems like most of the Scrum articles […]
Should programmers talk with customers / users according to MSF / agile methods?
I’ve just read two statements that seem to be very different:
Combining KanBan in a SCRUM process
Does anybody have an experience in combining KanBan in SCRUM, could this work, would this make sence or would it be an overdesign?
How to write user stories for a framework API
I need help understanding what user stories should look like for a web testing framework we are building for our organization’s QA department. We are trying to run this project using Scrum.
How can architects work with self-organizing Scrum teams?
An organization with a number of agile Scrum teams also has a small group of people appointed as “enterprise architects”. The EA group acts as control and gatekeeper for quality and adherence to decisions. This leads to overlaps between the team decision and EA decisions.
Shared QA responsibilities on an Agile team
For many years our IT development group subscribed to the waterfall software development methodology with segregated pods of programmers specializing in database development, logic layer and presentation layer development. Of course we also had a small quality assurance group which handled all testing responsibilities. Requirements, tasks and bugs were handed back and forth electronically, very little conversation took place, and the process ground painfully on.
Can we pull future user stories in current sprint?
Suppose we have estimated 5 user stories to complete in a sprint and completed all of them with testing, buffer time and for expected bugs.
Planning poker, individual or whole group in estimates?
In planning poker/scrum poker, when an estimate is made, should the estimate be made based on the assumption that only a single developer is assigned to that task, or a group of developers? If the latter, how large is that group? The reason this is relevant is that the time estimates would probably be different if a single person works on the problem compared to having several people. I’ve read several descriptions of how planning poker is supposed to work, but this basic information seems to be omitted, as if it should be inferred from the procedure in some way.
Scrum: What to do with epics once the stories are clear?
When working on a backlog, you define epics and break them down into user stories. Epics are estimated and kept on the backlog as epics until they become important enough to be planned into one of the next sprints.