Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 15180

An agile framework within which a Product Owner (PO), Development Team (DT) of 3-9 Developers and a Scrum Master (SM) work as the Scrum Team (ST) to build and sustain complex products of the highest possible value. They do this work within a timebox called a Sprint; Sprints may be shorter, but may not last more than 30 days. Events, roles and artifacts are described definitively in the official Scrum guide: http://scrumguides.org/scrum-guide.html

0
votes
you would expect an open-minded self-organizing team to reach that conclusion on their own. The only challenges that remain within the few constraints that Scrum imposes: Delivering functionality at …
answered Jun 25 '14 by Kris Van Bael
2
votes
I concur with all answers above. In the heat of commercial reality, the PO will keep on prioritizing functional stories over technical ones. Often to the frustration of the team. The team should ref …
answered Sep 25 '12 by Kris Van Bael
1
vote
release planning and it is worth investigating: Is the "definition of done" too weak and the team is piling up left-over work from previous sprints? Is the organization getting better at diverting scrum
answered Feb 5 '13 by Kris Van Bael
14
votes
With "item", I suppose you mean "task". Planning optimism in software is as old as software itself. The good thing about scrum is that you are facing it soon and create visibility of it: this is why …
answered Jul 9 '13 by Kris Van Bael
5
votes
it allows for early feedback, not just from customers it keeps management from getting nervous (they can 'see' the progress) it keeps the dev. team into a good habit And most important (at least in …
answered Feb 1 '14 by Kris Van Bael
4
votes
Apply the "potentially shippable" rule as far as it makes sense. Use your common sense where it doesn't. (Common sense is sometimes called "rule 0" in agile) A team should avoid to commit work that i …
answered Mar 1 '14 by Kris Van Bael
4
votes
The level of detail at the planning meeting depends a lot on the personality and expertise of the PO. Take user interface as an example: Some product owners have strong UX skills or use UX experts ou …
answered Jul 8 '14 by Kris Van Bael
1
vote
If you feel that you can completely finish another story, then have a chat with your product owner to select the right one. (a small ad-hoc re-planning meeting) Otherwise, spend that time well to pre …
answered Mar 14 '13 by Kris Van Bael
2
votes
I have two places (as the product owner) New feedback from customers can translate in more stories, a change of story priorities or some new details about a story. In the back log I take notes of the …
answered Apr 29 '13 by Kris Van Bael
10
votes
we just got through such an experience (me as scrum product owner). It took us two years to get to something releasable. But still, agile brought us many benefits. First: A total rewrite is by …
answered Oct 31 '12 by Kris Van Bael