Many candidates:
Ignore Agile questions.

Skip mock exams.

Memorize instead of understanding concepts.

Don't review incorrect answers.

Your mistakes during practice tests are your best teachers.

Technical knowledge is important, but these skills matter just as much:

• Communication
• Conflict resolution
• Stakeholder management
• Time management
• Decision-making

One thing I wish I'd understood earlier is that the PMP exam isn't based on memorizing the PMBOK® Guide alone. The PMP Examination Content Outline (ECO) is what defines the knowledge and skills the exam is designed to assess.

A lot of candidates spend weeks reading every chapter they can find but never compare their study plan against the ECO. Once I started using the domains, tasks and enablers in the outline to organize my preparation, my study sessions became much more focused. It also made it easier to identify weak areas instead of reviewing topics I already understood.

If you're just starting your PMP journey, I'd recommend building your study plan around the Examination Content Outline first, then using books, videos and practice questions to support each domain rather than studying randomly.

I wrote a guide explaining the PMP Examination Content Outline in more detail. If you'd like additional guidance, you can read it here: https://www.snsccs.com/blogs/pmp-examination-content-outline.

I'm interested in hearing how others structured their preparation. Did following the ECO change the way you studied, or did you rely on a different approach?

Many people expect scheduling and meetings.

What part of the job surprised you the most after moving into project management?

Meeting notes ● Status reports ● Risk brainstorming ● Email drafts ● Task summaries Always review AI-generated content before sharing it.

Leadership wants us to grow the project services side now. Traditional IT consulting, some app dev, cloud migrations, transformation-type stuff. Mix of fixed milestone and T&M.

For anyone who’s tried to run actual project work through Halo:

Does the project module hold up under real project delivery, or does it feel bolted on next to the service desk

Resource planning across a 50 - 60 people. Is it there or are you exporting to Excel?

Utilization and margin reporting at the project level. How deep does it go?

Where does it hold up? Where does it fall apart? Anyone move off it to Kantata, Scoro, Projectworks and never look back? Anyone try one of those and wish they’d gone with Halo?

Anyone try to run this in Halo, give up, and move to something else?

Trying to figure out if we push harder on Halo or accept we need a second tool for project delivery.

Leadership wants us to grow the project services side now. Traditional IT consulting, some app dev, cloud migrations, transformation-type stuff. Mix of fixed milestone and T&M.

For anyone who’s tried to run actual project work through Halo:

Does the project module hold up under real project delivery, or does it feel bolted on next to the service desk

Resource planning across a 50 - 60 people. Is it there or are you exporting to Excel?

Utilization and margin reporting at the project level. How deep does it go?

Where does it hold up? Where does it fall apart? Anyone move off it to Kantata, Scoro, Projectworks and never look back? Anyone try one of those and wish they’d gone with Halo?

Anyone try to run this in Halo, give up, and move to something else?

Trying to figure out if we push harder on Halo or accept we need a second tool for project delivery.

 Everyone seems to struggle with different topics while preparing for PMP.

For me, stakeholder engagement took a while to understand.

Which concept was hardest for you, and what finally made it easier?

Simple habits that make a huge difference:

Start meetings with a clear agenda.

Document every important decision.

Identify project risks early instead of reacting later.

Good communication solves many project problems before they grow.

Hi everyone,
I’m 26 years old and currently in the U.S. on an F-1 student visa.

Background:
- Bachelor’s in Psychology
- Currently pursuing a STEM Master’s in IT Project Management
- Expected graduation: December 2027

I’m intentionally trying to build a career in project management, but I don’t have formal PM experience or a software engineering background.

If you were in my exact position today, what would your strategy be between now and graduation?

Specifically:
What types of internships should I prioritize?
Which certifications are actually worth getting before graduation (CAPM, Scrum, etc.)?
What technical skills should I learn?
Are there conferences or networking events you’d recommend?
If you had about 16–18 months before graduating, how would you spend that time to maximize your chances of landing a strong first PM role?

Thanks in advance, I genuinely appreciate any guidance.

Soy Pm TI con amplia experiencia y soy de Costa Rica.

Algún colega tico que sepa de alguna oportunidad, por favor DM

AI can assist with: ● Meeting summaries ● Risk identification

● Task prioritization ● Drafting project documentation ● Status reports It saves time but still requires human judgment.

Hi everyone! I’m currently looking for my next opportunity and wanted to see if anyone knows of teams hiring or would be willing to provide a referral.
I have 6 years of experience leading complex healthcare IT and digital transformation initiatives. I’m PMP-Certified, a Certified ScrumMaster, and have managed enterprise initiatives involving clinicians, executives, vendors, and technical teams from planning through implementation.

My background includes:
Healthcare IT Project Management
Agile & Waterfall delivery
Scrum Master experience
EHR implementations and integrations (Epic/Cerner)
Telehealth implementations
Vendor management
Cross-functional stakeholder leadership
Go-lives, system implementations, and operational process improvement

I’m primarily looking for:
IT Project Manager
Senior Project Manager
Technical Project Manager
Healthcare IT Project Manager
Digital Transformation Project Manager
PMO roles

I’m open to remote positions. Healthcare is my strongest background, but I’m also interested in SaaS, technology, consulting, and other industries where strong project management skills are valued.

If your company is hiring or you know of any opportunities, I’d really appreciate any recommendations or referrals.
Feel free to comment or send me a DM.

Thank you so much, I truly appreciate any leads!

Helpful habits: Understand stakeholder expectations early. Communicate regularly. Listen before responding. Document action items. Follow up consistently. Trust is built through communication.

The part nobody prepares you for is the day after the workshop. Half the room remembers one thing, the other half remembers another, and your sponsor asks for a summary by noon. You are not writing down decisions, you are negotiating them with bullet points.

I started recording client sessions a couple of years ago. I mention it in the agenda, and I offer to share the transcript if they want. The recording itself is not the deliverable. It is insurance.

My actual workflow now depends on the setting. For in-person workshops I record on my phone, then upload the audio to vomo ai afterward and pull a transcript plus the action items. For remote calls I just open vomo ai in the browser and record there. Either way I cross check my notes against the transcript. If there is a dispute I can quote the exact moment and we move on instead of cycling for a week. It has saved two projects that were about to go sideways over misremembered scope.

I still write the final recommendation myself. The transcript just keeps me honest about what was actually said and what I am adding after the fact. It is not perfect, but it is better than three people confidently remembering three different meetings.

Before using AI outputs:

Verify facts. Check confidentiality. Review recommendations. Add human context. AI is powerful, but review is always necessary.

AI can help with: Creating meeting minutes Drafting reports Organizing tasks Summarizing long documents This gives project managers more time for planning and team collaboration.

Hi Everyone , I am currently working on developing the employee performance review framework for project manager ,trying to understand how the performance of the project manager is measured so that i can create measurable KPIs.

KPI like Project Delivery,Project Quality,Risk management ,Issue resolution,Documentation,Collaboration,Process improvements,Learning & certification.

What metrics or evidence do you use to evaluate performance?

What would you say is a "must learn first" concept or skill for project management for newcomers to this profession?

The uncomfortable answer is that updating the tool is probably no one's actual job. It's everyone's implied job, which means it loses to real work every single day, and honestly it should.

What worked for shops I've been in: stop asking everyone to keep everything current. Name one person whose job is a 15-minute weekly pass asking "what on this board is no longer true?" They don't update everything themselves. They just flag what's stale and chase down the truth on the few things that matter.

The team usually stops hating the tool once it stops being a chore everyone shares and starts being one person's short, defined task.

One thing worth checking before you change anything, though: is it that they don't update it, or that they update it and nothing ever comes of the updates? Different problems. The first one is the fix above. The second one means the updates go into a void, and people quit updating tools no one reads. That one gets fixed by you, not them.

When I was preparing for the PMP exam, I realized I was making the same mistake I see on many projects I had plenty of resources but no clear plan.

The approach that worked best was treating exam preparation like a project. I set a realistic timeline, broke the syllabus into manageable milestones, tracked my progress each week and adjusted my study plan whenever I fell behind. Instead of trying to memorize everything, I focused on understanding how the concepts apply to real project situations.

Regular practice questions were useful, but reviewing why I got an answer wrong was even more valuable. That helped me identify knowledge gaps early instead of repeating the same mistakes.

If you're interested, you can read it here: https://www.snsccs.com/blogs/how-to-prepare-for-pmp-exam.

I'd also be interested to hear how other project managers approached PMP preparation. Everyone seems to develop a different system and it's always useful to compare what actually works in practice.

I'm struggling with something in my role, and I'm wondering if this is just how every organization operates.

We have dashboards. We have status meetings. We have reports.

But I still feel like the team often knows something is changing long before leadership has enough confidence to do anything about it.

By the time everyone agrees there's a problem, we're already reacting instead of preventing.

Does your organization do this differently?

What questions help you understand whether an initiative is actually healthy before it officially shows up in reporting?

Imagine your project management tool could use AI for anything. What feature would save you the most time?

Leadership wants us to grow the project services side now. Traditional IT consulting, some app dev, cloud migrations, transformation-type stuff. Mix of fixed milestone and T&M.

For anyone who’s tried to run actual project work through Halo:

Does the project module hold up under real project delivery, or does it feel bolted on next to the service desk

Resource planning across a 50 - 60 people. Is it there or are you exporting to Excel?

Utilization and margin reporting at the project level. How deep does it go?

Where does it hold up? Where does it fall apart? Anyone move off it to Kantata, Scoro, Projectworks and never look back? Anyone try one of those and wish they’d gone with Halo?

Anyone try to run this in Halo, give up, and move to something else?

Trying to figure out if we push harder on Halo or accept we need a second tool for project delivery.

I'm curious how different organizations are approaching this today. 

For those managing SAP transformation programs: 

• How do you track progress across multiple workstreams? 
• How do you keep business, functional, and technical teams aligned? 
• What tools do you use for reporting and stakeholder visibility? 
• What becomes the biggest challenge as projects grow? 

I'm asking because enterprise SAP programs often involve multiple teams, vendors, and stakeholders, making visibility increasingly difficult as delivery scales. 

I'd be interested to hear what's worked well for your teams, what hasn't, and what you'd do differently on your next implementation.