So I've had to miss the last few weeks, but it looks like the Friday #pmchat tradition has died?
A8: Transition planning. You have to know who is taking responsibility for what parts of rollout and also on-going support after the project. What's the training/documentation? Just throwing something good out there doesn't mean it will be understood without help. #pmchat
A5) Not PM-specific: Managing email and marking+tracking the tasks and follow-ups that come from email. Investing time in finding & following a good process for this will repay in spades. #pmchat
A4) If you have PM's in your org, talk to them about what they do and what they want you to know about what they do. You'll get org-relevant info and build a working relationship at the same time! #PMchat
A2) PMs are often perceived to be roadblocks, rulemongers, and meeting fanatics. But sometimes slowing down to take stock or prevent/solve a problem, following a tried and true process, or having a face-to-face is a tool we're using to try to ensure things go right. #pmchat
A1) So many different kinds of things can derail projects or even cause them to fail. Understanding the breadth of fundamentals can help you prevent, foresee, identify, and mitigate these many (potential) problems. #pmchat
Katie joining #pmchat here from near Portland, OR USA and chugging coffee as quickly as possible.
Katie arriving late to #pmchat for the next hour. My VPN dropped right at the top of the hour! Took a hot minute to get it back.
Q8: This says what I would say far better than I ever could: xkcd.com/936/ #pmchat
A7: Like I mentioned before, we have to incorporate regulatory considerations (including privacy & security) into what we build/configure--and account for that in user trainings, etc, for handoff to ops. #pmchat
A7: We use a cloud file/doc mgmt system that is FERPA/HIPAA compliant. As PM, I spend quality time setting up folder shares so people only see what they need and have rights to see. #pmchat
A5: This is part of our initial project request analysis--before initiation can begin. #pmchat
A4: Hey, US orgs are impacted by this! We exchange students with the EU and the UK all the time. We're still trying to figure out the implications. #pmchat
A3: Besides training end-users as much as possible? Patch currency (management tools to enforce if possible) and application whitelisting come to mind. #pmchat
A2: My organization is a higher ed institution that also operates clinics. We have both student and patient privacy to account for in all of our information & tech projects #pmchat
A2: I would have to say about the same. Awareness is a constant--knowledge and tools are ever increasing. #pmchat
A7: For scripted testing, document expected results in advance. Preferably have the test steps performed "blindly" (i.e. user cannot see expected results info when reviewing the results). Helps to prevent user seeing what they expect to see--overlooking an actual problem. #PMChat
A6: I ask users what their "problem children" scenarios are--the complex ones that are challenging. Knowing the 20% outliers helps to avoid actual "show-stopper" situations where that 20% literally cannot be worked around in a new solution. #pmchat
Re Q5: Do you mean one-time questions at the start of a project, one-time? Or do you mean repeat questions at on-going periodic meetings? #PMChat