Tag Info

New answers tagged

2

Just to rephrase the question. You are blocked on scrum adoption because of the bug in JIRA? That sounds very wrong to me. Scrum is a project management methodology, it cannot depend on tools, tools are meant to be assisting with routine work, not impede it. Hence, my always advice, use physical board, see the progress looking at real tangible things. ...


0

It depends. The level of details in acceptance criteria may very depending on the type of story. Consider creating a user story for a web page or for a new programming language? I suppose different level of details will be needed to accept the story (meaning it is done correctly). I find that the more detailed the AC are, the less are the chances of ...


5

Personally, I would say an acceptance criteria of "Must be an <h1> tag" is not an appropriate acceptance criteria, unless the PO would be willing to reject the story if the team used some other tag and applied styling to make it look like an <h1> tag. In other words, is the use of <h1> truly a required part of the solution? I would ...


0

Here is a script that I prepared that will look through the workitemhistory view to work out when an iteration changes on a date which is between the iteration start and end date. It is a work in progress, but it demonstrates that the answer is there if you need it. DECLARE @iteration VARCHAR(300) DECLARE @startDate DATETIME DECLARE @endDate DATETIME ...


0

Some devs that were used to working under the old system complain that this doesn't give the developers credit for completing the work that they were assigned Did they really complete the work in time when there is not enough time left in the sprint for completing the test cycle? Maybe, maybe QA needed more time than expected, who knows, but the ...


2

It is your team's responsibility -- the whole team -- to make sure everything is done. If the devs are finished coding and there are still tests to write or perform, they should pitch in and help the testers. There shouldn't be any "open developer time" -- why penalize your testers by giving the developers free time? The developers need to help with the ...


6

The official Agile answer is that this simply should not be allowed. Unfortunately, as you are experiencing, the reality is that this often happens. Sometimes this is because business requirements change too rapidly even for short sprints. Sometimes this happens because of pure bad planning on the part of the product owner. And unfortunately sometimes ...


3

Scrum asks for an ordered backlog, not just a prioritized one. MoSCow can help you to do a course grain prioritization, but you need an ordering for a Scrum backlog. You could use MoSCoW to help you define an MVP but you will ultimately need to sort your backlog as Scrum would suggest. Using MoSCoW long term in Scrum doesn't make sense because the scope ...


3

In Scrum, requirements go in user stories. The product owner is responsible for talking to all of the stakeholders and gathering requirements. There is generally no single requirements document at all, nor any overall project report similar to what you describe. A user story will describe the requirement at the highest level with a single feature with a ...



Top 50 recent answers are included