5

I find it helpful that the site embraces both classic and agile approaches. I'm relatively new to project management and to agile, and I work in an environment in which classic PM is still expected once we hit a certain point up the management chain. It is helpful to have both discussed so as to learn both languages, compare&contrast strengths & ...


5

While there is merit in your suggestion but such efforts have failed to gather traction in the past. New Stack Exchange sites thrive on traffic and good content. There were such proposals on Area51 but got closed due to low activity. Here are four examples: http://area51.stackexchange.com/proposals/7794/scrum http://area51.stackexchange.com/proposals/15585/...


4

TL;DR Most of these questions will be off-topic. There may be occasional exceptions, but I wouldn't hold my breath. The question cited was answerable, but I personally consider it a poor-quality question. It could have easily led down a rabbit hole, but in this case did not. I'm inclined to leave it open, but would certainly revisit this particular ...


3

I see this in a slightly different approach. What's more important? To accept as valid some questions that cannot have a canonical answer or to leave the community without any answers at all? I'd support the former. My reading of "off-topic" for general terminology was to avoid questions that are broadly answered all over the internet: "what's agile?...


3

TL;DR Use tags such as scrum, pmbok, or prince2 to tag questions and filter your searches for a more optimal experience on PMSE. Questions here cover a wide range of frameworks, and represent a broad cross-section of industry experience. Analysis Scrum, Kanban, and Lean are examples of project management frameworks and methodologies, but there are ...


3

Project Management Stack Exchange is for questions about the field of project management; thus, questions about ISO documentation and ISO structure don't seem like things that would be on-topic here. What's more, our site does best when there's a real, actual problem to be solved. In this case, you're looking for links to documentation, which is really ...


2

I guess my main message is, we are not serving classic pm nor Agile much good by mixing both topics. Questions and answers should be addressing real-life PM problems, regardless of being waterfall / agile (or lean, or Kanban) projects... maybe, a problem faced in a waterfall project could have its solution in a agile methodology. The other way round is ...


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