Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 months ago.
Improve this question
following the origins of the agile scrum tests certification, the response of this question :
"scrum master and product owner can be the same"
is different.
When I read the official scrum guide I don't find any text about this assertation.
How to know the very official response of this question ?
What is the response ?
Dealing with release of the certification the response can be different ?
The "official" response per the Scrum Guide may be summarised as: "If it does not exclude it, then it can be done.
But just because you can, doesn't necessarily mean that you should.
While the Product Owner and Scrum Master can indeed be the same person, I strongly discourage it. This is because the two roles have conflicting accountabilities and it is wholly unreasonable to expect one person to have to balance them.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Is there a standard list of criteria that we need to validate before we can, say, "consider" a particular epic for an iteration. I was referring to maybe a checklist or a set of questions that we need to ask ourselves / product owner.
BACKGROUND: I am trying to set up a Agile process which will not be individual dependent and hence the need for a checklist.
Almost by definition, an "epic" is simply a placeholder for some desired functionality. It contains very little detail and so, would not be considered for an iteration.
The "epic" needs to be broken down into smaller product backlog items that do contain enough detail, are therefore estimatable and are small enough that they can be completed within an iteration. (In fact, I usually recommend teams I work with make product backlog items small enough that between 5 and 15 can be taken into a sprint).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I have a company website hosted at www.BRAND.com (where BRAND is a generic name).
The company want to develop a "micro website" for one of their campaigns, named "Inspired By BRAND".
I have two directions:
inspired.by.BRAND.com - which I personally don't like too much. I don't know why but I don't recall any web address similar to this one subdomain.subdomain.domain.com.
inspired.BRAND.com - which I this is best suited for it. Fewer dots and similar to "more friendly" addresses subdomain.domain.com.
Any hints, guidelines, any thoughts is well appreciated.
Thanks in advance
Personally, I would probably go for inspiredby.BRAND.com. It reflects the name of your micro-site, sounds good to me, and is communicated easily by phone as it does not have any hyphens or underscores etc...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Both theses work items seem (at least to me) to be interchangable, with the possible exception that work items may be usable for non-defect changes (such as new functionality).
Is that all there is to it, or is there some more fundamental difference between the two?
A Task is an an over-arching work item type meant to encapsulate a piece of work that does not fall under the umbrellas of the other work items (Defect, Story, Bug Report, and Feature Request, by default). Typically, new functionality would fall under the Feature Request umbrella.
Work items that might be good candidates for Tasks might include:
researching the capabilities of a library you are considering adopting,
building a new test client, or
filling up the soda machine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Does anyone happen to know if Joint Application Development is categorized under Agile methodology or are they two separate development processes? It appears that SCRUM is a type of agile but JAD is related to RAD and is outside of agile.
Any information on differences are appreciated.
Agile is not a methodology in itself. It is a set of guidelines (the manifesto), a mindset, a way of approaching software development. SCRUM is one manifestation of that as a concrete methodology.
JAD (it appears from Wikipedia) is related to requirements gathering in DSDM. DSDM is typically classed as an agile methodology so I guess your answer is there.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
In agile manifesto and in many answers here, I found this :
Individuals and interactions over
processes and tools.
So, what exactly does it mean?
In my opinion, processes and tools are important part of software development. For example, what is the point of installing continuous integration if people are going to ignore the result for weeks?
Even the best tools and processes add little value in the hands of inept people.
Focus on building and training a good team vs. buying into the lastest tool/process and hoping it'll solve all your problems.