Please login or join to subscribe to this thread
It depends partly on the vision/leadership you'll bring to the company, and partly on the company's existing culture/leadership. If you/they are dynamic, fast-paced, continuous-learners who embrace best-practices, worked well in a matrixed way, etc., go for Agile! If the organization is more cautious/traditional, perhaps start with waterfall that's easier for most people to comprehend and not as "radical".
I'll be interested to read what others write in response to your question. Good luck and please report back in 6 months which way you went and the results.
First of all, PMP does not mean waterfall. Agile or waterfall is independent of project management.
As far as which one to choose, I would go with both. Where requirements are known and stable, predictive is faster and cheaper. Where requirements are unknown or volatile, agile allows you to deliver value quickly and flexibly.
Interesting this your question
Thanks for sharing
Much depends on the culture of your organization and the development approach dictated by management
I am convinced that for the specific project to which you refer you can use a hybrid approach
What are the current development and release processes? How are requirements for enhancements currently managed? Will this involve one team, or multiple teams?
You're probably going to hear from someone about how there is no agile methodology. I'm assuming you mean Scrum. Will it be a single team, or scaled scrum? (or whatever approach you use)
What will the organization look like once you have this approach in place?
I recommend starting with the vision for how you think it should work, and then work through the opportunities and obstacles your approach will bring to the surface. You may find one approach fits your organization better than the other, or you may find that you can start with one and need to evolve into the other.
If you're looking at single-team Scrum, that will be much faster to implement and get people up to speed than a scaled Scrum approach.
Thanks to all for your insightful replies. I was thinking a hybrid approach would also be the best path. This is a pharmaceutical company, therefore there is more oversight (medical, legal, regulatory) perhaps vs other industries. I have a friend who works for another pharma company in digital and told me they have Agile in place (Scrum). She said it would be difficult to implement Scrum because it would require many resources and unless it was already in place, would probably take too long to set this structure up.
I'll be working with agency(s) on the UX, front-end development, brand experience, and other KPIs to grow business impact.
My original question around PMP vs Agile was due to my understanding that PMP certification primarily relies on Waterfall approach that is more traditional but can be more rigid. Agile (Scrum or Kanban) is embraced more in software development and allows for more fluidity and flexibility. Since the project is digital marketing based, it seemed like some sort of hybrid might make the best approach to allow for flexibility with the web hub experience but also successfully track/execute scope, budget, time requirements. I've heard PMI offers PMP cert (based on Waterfall) and PMI-ACP (based on Agile approach). My primary role is as a digital marketer and digital strategy leader so getting both certs seemed like a lot of work since I also need have deep expertise in SEM, SEO, UX/UI, Web Analytics, Adobe Experience Cloud and Data Science (predictive analytics, machine learning, etc.).
I have past experience managing digital and health technology projects but haven't formerly incorporated a PM methodology before and would like to moving forward. I've taken a preliminary PM intro certification that's given my a broad overview but thought getting a PMI cert might add additional value for my career.
I know the company has access to Microsoft Project so was going to utilize that software as well.
You should also realize that Scrum is limited to product/service delivery. Scrum doesn't deal with financial management or stakeholder management, amongst others, which are project management areas.
PMI's PMBOK Guide is a subset of the project management "body of knowledge". Unlike Axelos' PRINCE2, it is not a methodology. The PMBOK Guide provides you with guidance, direction, tips, and suggestions. You take from it what makes sense for you and your organization and create your processes and tools.
On every web project I've been a part of, an iterative and incremental approach has produced a higher quality product at a faster rate. This is due to the nature of web development. The business probably doesn't know exactly what it wants, yet, and they won't have any feedback from their customers until they have some part of the product in place. Rather than wait until all your requirements are gathered and estimates approved by the business, you should start on the work you know you can do and deliver what you can. Ideally, this should help you answer questions about the product so you can continue development.
In a stereotypical "waterfall" or predictive project, you couldn't properly start development until your project gets approved, which requires defined scope, budget, and schedule. Then you'll deliver product in large chunks and go through a change control process when you get the user feedback. Better to anticipate those changes.
I'm speaking in very broad generalities and there's more to being "Agile" than working incrementally, but I think that's your main question. I would definitely recommend that approach.
As it doesn't seem like the department has a pre-defined PM approach in place, I was wondering if I should prep with acclimating to particular methodologies prior to starting the position and whether it would be helpful to pursue any formal certification.
Please login or join to reply