This podcast is part a published article on The Digital Project Manager. You can read the entire article here.
Clarizen, a leader in enterprise project management software and enterprise projects, brings you this podcast.
Clarizen.com has more information
Similar Links:
Clarizen – Project Management Software
16 Amazing Project Management Software Tools
How to Estimate Projects: The Complete Guide to Project Budget & Cost Estimation
Agile Vs Waterfall. Which Methodology Should You Use for Your Project?
How to Estimate Projects: The Complete Guide to Project Budget & Cost Estimation
Project Management Training – The Digital School for Project Managers
Project Management Resources
Join our Slack project manager team
Audio Transcription:
Ben Aston:
The DPM Podcast is where we go beyond theory and offer expert PM advice to help you lead better digital projects. Thank you for listening. I’m Ben Aston. Let’s be real, has your client ever said to you, “Hey, that was it, that’s exactly what we wanted. It’s exactly what you said at the beginning. And it’s amazing, how you managed to capture everything and not lose anything along the way?”
It hasn’t, I suspect. It’s likely that your requirements weren’t properly defined. How can you manage requirements to avoid getting in trouble later in the project? Give the client and developer the information they need to do the job. Today’s podcast is about project requirements.
How we define a project and what functionalities are required for clients to understand what’s being delivered. Requirements are, in essence, a communication tool. However, they can be difficult to define correctly. If you make them too strict, you might find that there are many things missing. How can we achieve this balance?
Kelly Suter is my guest today. Kelly is a technical manager at BI Worldwide and one of our resident Deakin specialists at the Digital Project Manager. So, Kelly, how are you?
Kelly Suter
Hey Ben, thank you for having me.
Ben Aston:
It’s great to have you. This is probably our second podcast, I believe.
Kelly Suter
Yes.
Ben Aston:
A podcast was produced a long time back. For those who may have lost their identity, can you give us a brief overview of how you got into project management. It’s not dissimilar to most project managers, I think. Although we never planned to become project managers when we were children, tell us about your journey and how you became a digital PM.
Kelly Suter
Yes. I started my professional career as a sports reporter. However, because I studied Communications with a concentration in media and public relations, I decided to look into the publicity industry. I was a publicist for three years for Sesame Street Live. I had someone who was at an eCommerce shop, a full-service digital agency, that focuses on eCommerce.
So, she said, “We don’t have a department for project management here, and would you like to be a manager?” And I replied, “What is that?” My dad had a graphic design agency so I was well-acquainted with the agency process. It was chaotic, always going. But I was like, “Yeah, that’s what I’m into!”
