New PM Articles for the Week of September 11 – 17

New project management articles published on the web during the week of September 11 – 17. And this week’s video: the folks at MePIN provide a little background on the GDPR, if it’s not already on your radar. Just 2 minutes, safe for work.

Must read (or Listen)!

  • Lily Hay Newman gives us some background on the Social Security number—why we still use it for so many things and what the Equifax breach might mean for our American identity crisis. 5 minutes to read.
  • Russell Brandom diagnoses the larger problem: our entire credit bureau system, which relies on data that is no longer private, is irretrievably broken. 4 minutes to read.
  • Bertrand Duperrin notes measures of a lack of business maturity in data privacy and security practices, even with the General Data Protection Regulation becoming effective in May 2018. 3 minutes to read.

Established Methods

  • Harry Hall explains why those who already have their PMP should read the PMBOK 6th edition. 2 minutes to read, and I second the motion.
  • Elizabeth Harrin reviews The Project Manager’s Little Book of Cheats, by Beth Spriggs. “I’ve covered it in sticky notes.” 2 minutes to read.
  • Johnny Beirne interviews Mike Clayton on the importance of project definition. Podcast, 28 minutes.
  • Ron Rosenhead notes the potential value in a selection process for project sponsors. 2 minutes to read.
  • Cheryl Texeira walks us through planning a project with an unrealistic deadline. 3 minutes to read.

Agile Methods

  • Stefan Wolpers curates his weekly list, from Agile metrics to scaling Agile, to the existential question: Is Agile Doomed? 11 outbound links, 3 minutes to scan.
  • Mike Cohn maps out the most productive way for programmers and testers to collaborate. 7 minutes to read.
  • Johanna Rothman continues her series on alternatives for Agile and Lean road mapping, describing the Product Value Team. 3 minutes to read.
  • Mishkin Berteig lists three alternatives to Scrum and identifies how well each fits IT project work. 8 minutes to read.
  • Bart Gerardi describes the benefits of an Agile Center of Excellence as opposed to a more common Project Management Office. 7 minutes to read.
  • Scott Sehlhorst describes an approach for progressively elaborating the team’s understanding and behavior model of the users. 6 minutes to read.
  • Jason Moccia tutors us on design sprints, which use Scrum to refine the requirements and design before beginning development. WaterScrum? Uh, no. 7 minutes to read.

Applied Leadership

  • Uri Galimidi tells an anecdote about a manager who failed to hear what he was being told and offers some thoughts on developing your listening ability. 4 minutes to read.
  • Art Petty describes the corporate Zombie Apocalypse and offers some head-shots to deal with the causes. 3 minutes to read.
  • Ted Bauer eviscerates the “high achiever” myth, with acerbic wit, foul language, and several anecdotes. 6 minutes to read.
  • Suzanne Lucas gives us the executive micro-summary of a study conducted by an all-women team at BCG on what is helping women succeed and what is not. 3 minutes to read.

Technology, Techniques, and Human Behavior

  • Ryan Ogilvie shows how to sell service improvement to decision makers as a value-add. 3 minutes to read.
  • Steven Levy profiles the team at CTRL-Labs and the work they’re doing on a brain-machine interface that might soon be implemented as a watchband. 15 minutes to read, but absolutely worth it.
  • John Goodpasture links Oren Etzioni’s rules for AI systems with Isaac Asimov’s laws of robotics for an interesting baseline of constraints. 2 minutes to read.

Working and the Workplace

  • Mike Griffiths expands on Dianna Larson’s recent keynote speech, “Knowledge work is learning work.” 4 minutes to read.
  • Adam Schwartz, founder and CEO of Articulate, tells us why (and how) remote work scales. 5 minutes to read.
  • Conner Forrest reports on a recent survey by Softchoice: 74% of office workers would change jobs to firms that supported working from home. 2 minutes to read.

Enjoy!

New PM Articles for the Week of August 14 – 20

New project management articles published on the web during the week of August 14 – 20. And this week’s video: Erica Olsen gives us a fast tutorial on how to conduct a SWOT analysis. Just over 5 minutes, safe for work.

Must read (or Watch)!

  • Dave Prior interviews Mike Griffiths and Johanna Rothman on the soon-to-be-released PMI Agile Practice Guide. Johanna defines “Agile project manager” 14 minutes in and nails it. Video, 21 minutes to watch.
  • Jayanth Reddy and Pankaj Tiwari dig into the global changes disrupting India’s IT industry and ecosystem. A 15-minute read, but India is not a small country.

Established Methods

  • Elizabeth Harrin extracts 6 key principles from Louise Worsley’s new book, Stakeholder-led Project Management: Changing the way we manage projects. 2 minutes to read.
  • Harry Hall walks us through the process of creating a stakeholder register. 3 minutes to read; accompanying video is 4 minutes long, safe for work.
  • Elise Stevens interviews Catharine on managing diverse stakeholder groups. Podcast, 14 minutes.
  • Grace Windsor gives us a detailed class on how to work effectively with your project’s sponsor. 6 minutes to read.
  • John McIntyre points out half-dozen cognitive biases that PMO professionals should be aware of and be defending against. 6 minutes to read.
  • Barry Hodge tells us why our project will be canceled, and what we can do to prevent it. 3 minutes to read.

Agile Methods

  • Stefan Wolpers curates his weekly list of all things Agile, from “business Agile” (bad) to system resilience (good) and beyond. 12 outbound links, 3 minutes to scan.
  • Cornelius Fichtner interviews Joseph Flahiff, who claims that more projects are using Agile methods than ever before. Podcast, 29 minutes, safe for work.
  • Mike Cohn references the work of Richard Hackman on how authority can be distributed to teams, to support his definition of self-organizing teams. 3 minutes to read.
  • Kaysie Garza explains what to prioritize for a successful, scalable design process. 4 minutes to read.

Applied Leadership

  • Esther Derby shows why we need the virtue of patience when driving complex organizational behavior changes. 3 minutes to read.
  • Ron Rosenhead presents an anecdote that illustrates the need for self-awareness. You can’t change what you don’t realize needs changing. 3 minutes to read.
  • Mike Clayton provides a detailed overview of effective team communication. 10 minutes to read.

Technology, Techniques, and Human Behavior

  • Adrian Bowles presents a webinar on organizing data and knowledge using taxonomies and ontologies. 61 minutes, safe for work.
  • Kimberly Crawley interviews cybersecurity consultant Cheryl Biswas on the flawed state of readiness for cyber-attacks in small and medium-sized businesses. 10 minutes to read.
  • Karen Smith reflects on the power of questions. Is your question an invitation, a request, or a weapon? 4 minutes to read.

Working and the Workplace

  • Oliver Burkeman makes the case for the four-hour working day (like we needed to be convinced). 2 minutes to read, leaving you 238 minutes to work.
  • Patrick Allen suggests that your morning routine is just fine, but your unstructured afternoon needs work. 4 minutes to read.
  • Kat Boogaard reminds us what to do after meeting someone at a networking event. That’s why you went, right? 3 minutes to read.

Enjoy!

New Post at AITS: Simplicity

My latest article for AITS was published today: Simplicity: What’s Left When You Ignore Everything Else.

One of the great trends of the last decade has been the consumerization of virtually everything. You no longer have to know anything about the technology you are using to meet your needs. From retail self-service to manager dashboards to (soon) autonomous automobiles, our products are becoming ever less demanding of us, as we have become ever more demanding of them. And as project managers delivering those products to impatiently waiting end users, we have to understand the relationship between that expected simplicity and the hidden complexity in order to keep our projects within scope and on track.

As always, thanks for taking the time to read my stuff.