New project management articles published on the web during the week of November 7 – 13. And this week’s video: CEO of Datameer, Stefan Groschupf, talks about how companies like AirBnB, Uber and SpaceX are taking an Agile, evolutionary approach to data analytics. Just 2 minutes, safe for work.
Must read / view / listen!
Michael Hyatt argues that starting your day by eating a frog can help fight procrastination, but starting with the easiest task and working to the most difficult builds confidence.
Glen Alleman outlines the Agile Canon, as presented by Daniel R. Greening. This is an excellent depiction of Agile principles in five groups.
Jiwat Ram makes the case for compliance projects as strategic, “… as non-compliance could lead to far-reaching implications for business survival and continuity management.”
Elizabeth Harrin details the five skills you need to manage complex projects. She also explains the difference between difficult and hard projects.
Harry Hall covers the basics of requirements management.
New project management articles published on the web during the week of October 31 – November 6. And this week’s video: Melissa Marshall explains how to “Talk Nerdy to Me,” so we can share our complex engineering and technology work with others. In other words: your elevator pitch.
Must read / view / listen!
Aimee Chanthadavong reports on the success women in Australia are having in breaking the glass ceiling in tech companies and what the rest of the world can learn from them.
Dmitriy Nizhebetskiy provides a detailed explanation of how to conduct a qualitative risk analysis in a series of four videos totaling a little over nine minutes. Safe for work and recommended for viewing with your project team.
Art Petty explains how to survive and thrive with your executive sponsor. Just 28 minutes, safe for work.
Michel Dion puts the need for documenting requirements into perspective, as a vital communications tool.
Elizabeth Harrin lists three ways to reel it back in when your project starts to go off the rails. Note that these are not mutually exclusive, and in fact reinforce each other.
Harry Hall posts five questions to ask when developing a scope management plan.
David Hillson describes risk escalation, a portfolio-level approach to managing risk responses when the project that identifies the risk isn’t impacted by it.
Cornelius Fichtner interviews Beth Spriggs on her PMI Global Congress presentation: project assumptions as a source of risk. Just 23 minutes, safe for work.
John McIntyre proposes an interesting alternative to reviewing lessons learned documents when beginning a new project: it’s called Call3!
Ryan Ogilvie tells how incident management can be improved by those in other roles who have a stake in problem resolution.
Stefan Wolpers posts his weekly round-up of Agile articles, blog posts, and other content.
Johanna Rothman concludes her series on the roles of coaches and managers in Agile transformations.
Tom McFarlin on developer intuition: “It feels like all we’ve done is introduce complexity while championing simplicity.” Hear, hear!
Mike Griffiths does the financial analysis that shows when outsourcing / offshoring makes sense, and when it does not.
Austin Knight considers the sources of design debt (as opposed to technical debt) and how we can avoid piling up too much of it.
Brendan Toner reviews “Scrum Magic,” by Doug Purcell. An entry-level view of Scrum, with language friendly to project managers who use traditional methods.
New project management articles published on the web during the week of October 17 – 23. And this week’s video: Adam Grant’s TED Talk on the surprising habits of original thinkers and how to recognize them. Just 15 minutes, safe for work.
Kailash Awati case studies two examples of sensemaking using data science from two hackathons.
Alison DeNisco summarizes a report from Accenture and Girls Who Code that indicates the gender gap in tech is getting worse. But insights show how we can reverse the trend.
Andy Jordan points out a trend: some PM’s are feeling slighted because they get the “maintenance” projects while their peers get the strategic projects.
Suraj Chatrath notes that improving requirements gathering can reduce risk.