Tag Info

Hot answers tagged

8

This is the Product Owner's job. The whole point of the product owner is to act as the point of contact between all the stakeholders (including people like someone's boss's boss) and the team itself. In theory, the rest of the team should only ever have to deal with the Product Owner. The Product Owner goes and does all the work of talking to various ...


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 ...


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 ...


3

Note that in most articles, dedication means that the person is committed to the success of the project, not that the team is dedicated in a management sense. Example from the article you linked to, emphasis mine: [...] are dedicated to continuously improving their ability to deliver software Another example, from Successful Teams Are Small And ...


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. ...


2

More examples of interruptions will be helpful to understand the reasoning why your skip manager or another stakeholder requires "stop everything and do this" type of work. For "put a PPT together to approve", could this be the lack of transparency up? Does your team invite all the stakeholders to attend the demos showing the status/progress of sprint's ...


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 ...


1

Black-box testing means that the tester is not familiar with the inner workings of the system, while white-box testing is performed by someone who knows exactly how the program works. Both has advantages and disadvantages. Functional testing is testing whether or not the software product fulfills functional requirements, like "when loading an incorrectly ...


1

Black-box testing as opposed to white-box testing is a broad category of testing that includes tests where you do not know, and do not need to know, how the implementation works, you just want to test the outcome. For example: I click the buy button on a web site and the item I selected is now in my shopping cart. I don't care how the programmer made this ...



Only top voted, non community-wiki answers of a minimum length are eligible