A recent thread discussed the applicability of agile practices in traditional project management environments as described by the project management body of knowledge (PMBOK).
(This reporter apologizes in advance for the long quotes, this is an intense topic that was difficult to paraphrase.) Michael James quotes the PMBOK: About once per season I encounter the belief that the PMBOK doesn't contradict agile approaches. (reposting) Here are some quotes from the PMBOK Guide Fourth Edition suggesting the unsuitability of "project management" to product development with Scrum: It seems a bit brash if our recommendations to Project Managers is to not manage projects.
For example, if you were performing a research and development project, you wouldn't be doing implementation.
These new risks result from trade-offs made by the project team, and they need to be recognized, documented, and added to the project risk list.
A second type of project risk is that of not taking on the "right" project.
This free template is available for Microsoft Power Point 2007 and Power Point 2010 but you can also try to open it with backward compatibility as a Power Point 2003 template.
Instead of using a simple lifetime average, Udemy calculates a course's star rating by considering a number of different factors such as the number of ratings, the age of ratings, and the likelihood of fraudulent ratings.
To vent a little, I find APLN and the Agile COP interesting and reinvigorating, but I am not finding information that is applicable to my day-to-day work activities.