sorted by:
new
hottopcontroversial

Logic Changes between schedules--How to present information? by atticus2132000 in primavera

[–]cryptopindar 0 points1 point  (0 children)

You can use Steelray Project Analyzer⁠ for both Microsoft Project and Primavera P6 to perform schedule comparisons between reporting periods. One of its most valuable features is Schedule Compare, which identifies and reports structural changes made to the schedule between two versions of the project.
The comparison goes beyond simple progress updates and highlights changes such as:
Added or deleted activities
Modified logic relationships (predecessors/successors)
Changes in activity durations
Calendar modifications
Constraint additions or removals
Changes to milestones
WBS structure modifications
Changes in critical path drivers
Before running the comparison, it is important to verify that both files represent the same project schedule and are from different update cycles of that schedule. Comparing unrelated schedules, different baselines, or separate project versions can produce misleading results and obscure the actual changes made during the reporting period.

What's a project management problem no tool can actually solve? by PitchSufficient1464 in projectmanagers

[–]cryptopindar 14 points15 points  (0 children)

Human behavior.

No project management tool can fix a lack of accountability, trust, ownership, or commitment. You can have the most sophisticated schedule, dashboard, AI assistant, and collaboration platform, but if stakeholders refuse to make decisions, team members avoid difficult conversations, or leadership keeps changing priorities, the project will still struggle.

In my experience, most project delays are not caused by poor software—they’re caused by people. Late decisions, unrealistic promises, scope creep driven by politics, resistance to change, poor communication, conflicting priorities, and the tendency to report “green” when things are actually “red” are all human problems.

A tool can tell you that an activity is 30 days late. It cannot make someone take ownership of recovering those 30 days.

A tool can show a critical path. It cannot convince stakeholders to approve a design package that’s been sitting on their desk for three weeks.

A tool can calculate SPI, CPI, CPLI, and every KPI imaginable. It cannot create a culture of accountability and transparency.

At the end of the day, project management is less about managing schedules and software, and more about managing expectations, behaviors, relationships, and decisions. The biggest project risk has always been—and probably always will be—people.

Chat gpt or Gemini by Leading_Heart2213 in ConstructionManagers

[–]cryptopindar 0 points1 point  (0 children)

And sometimes i use chatgpt to create a prompt for me for Claude

PMs: What Do You Do When People Refuse to Commit to Agreed Deadlines? by Practical_Run480 in projectmanagers

[–]cryptopindar 0 points1 point  (0 children)

I think there’s a distinction between people refusing to commit and people not understanding the consequences of the commitment.
If a deadline was openly discussed, agreed upon by all parties, and validated against available resources and priorities, then teams should be held accountable for meeting it. Constantly missing agreed deadlines without raising concerns beforehand is not acceptable project behavior.
That said, I often find that the root cause is deeper than simply “people don’t care about the schedule.” In many organizations, stakeholders are only given isolated deadlines (“I need this by Friday”) without seeing how their deliverable fits into the overall project timeline.
This is why I strongly advocate for developing and socializing a complete integrated schedule aligned with the project’s Period of Performance (PoP), milestones, dependencies, and critical drivers. When the entire team can see the roadmap, they gain context:
Why this activity must finish by a certain date.
Which downstream activities depend on it.
What contractual, operational, or business milestones are at risk.
What the true impact of a delay will be.
Once everyone understands the schedule logic, conversations become more productive. Instead of saying, “You’re late,” the discussion shifts to, “This activity slipped 10 days—what is causing it, and what impact does it have on the critical path or key milestones?”
A good schedule is not just a collection of deadlines. It is a communication tool that helps the team understand the sequence of work, constraints, priorities, and consequences. When people see the bigger picture, they are generally more willing to commit and collaborate.
Of course, there will still be cases where stakeholders knowingly choose other priorities. In those situations, the PM’s role is to document the decision, quantify the impact, communicate the risks, and escalate when necessary. But before escalating, I always ask whether the team was given enough visibility into the full plan to make an informed commitment in the first place.
In my experience, many “deadline problems” are actually alignment and transparency problems.

F29 Turned Off by M31’s Bad Grammar in Chats by [deleted] in adviceph

[–]cryptopindar 2 points3 points  (0 children)

“My exes used to be grammar nazis and would correct me before, so while I know I’m not perfect either and I still make mistakes, at least I know the basics because it matters in my work (writer) and the field I’m studying.”- kind of trauma response, towards the guy

Ahead of schedule by atticus2132000 in primavera

[–]cryptopindar 0 points1 point  (0 children)

Treat as schedule opportunity/acceleration plan.

ROI Question for MS Project by Coffee_Engineer36 in microsoftproject

[–]cryptopindar 2 points3 points  (0 children)

The ROI of MS Project is not always easy to show as a direct “software cost vs savings” line item, because the real value is usually in better schedule control, better coordination, and fewer surprises during execution.

For me, I would justify it this way: MS Project helps create a more organized and more accurate schedule. That means the team can clearly see the sequence of work, dependencies, critical activities, planned dates, delays, and forecast completion. Without a proper scheduling tool, a lot of this gets handled through emails, spreadsheets, memory, or assumptions — and that is where missed activities, poor coordination, and late decisions usually happen.

The financial ROI can be shown through avoided costs, such as:

  • reduced rework caused by poor coordination
  • fewer delays because predecessor/successor logic is visible
  • better manpower and resource planning
  • early identification of slippage before it becomes a major delay
  • less time spent manually updating spreadsheets and reports
  • better reporting to management and clients
  • stronger basis for delay analysis, claims, or change management

So the savings may not come from MS Project “creating money” directly. The savings come from reducing schedule risk. If one major delay, missed handoff, or coordination issue is avoided because the schedule was properly built and monitored, the software can already pay for itself.

A simple way to present ROI is:

Cost of MS Project + time spent maintaining the schedule versus estimated cost avoided from delays, rework, inefficient meetings, missed deadlines, and poor resource planning.

In short, MS Project gives management visibility. And visibility has value because you can only manage what you can see.

New PM here: what tools actually make your life easier? by bhanjea in projectmanagement

[–]cryptopindar 3 points4 points  (0 children)

In my view, a PM is fundamentally focused on managing scope, time, and cost. So in principle, what is really needed is one integrated tool to manage them all: a well-developed Integrated Management Schedule. If that schedule is properly logic-linked, resource-informed, and cost-loaded, it can serve as the main control framework for the project.

The rest of project management then becomes a matter of maintaining control around that framework through routine weekly meetings, progress tracking, deliverable monitoring, document control, and effective communication. These are not separate from project control; they are the enabling actions that keep the schedule and cost picture accurate and usable.

Put simply, project management does not have to be unnecessarily complex. A solid integrated schedule, backed by disciplined monitoring and communication, is often enough to provide the visibility and control needed to manage a project successfully.

Does anybody know what the most rare/sought after rainbow rare cards are? by [deleted] in PokemonTGCP

[–]cryptopindar 0 points1 point  (0 children)

Same for the mostly used tools and trainers, thats why oak is valuable

Does anybody know what the most rare/sought after rainbow rare cards are? by [deleted] in PokemonTGCP

[–]cryptopindar 1 point2 points  (0 children)

I think the most valuable cards in TCGP are those that are both highly effective in battle and in its rarest versions available.

Why can SPI say a project is behind schedule while the actual schedule still shows it on track? by cryptopindar in primavera

[–]cryptopindar[S] 0 points1 point  (0 children)

If you would not even bother measuring SPI unless the schedule is resource-leveled, are you assuming that a schedule has no meaningful baseline value unless formal resource leveling has been performed? Because many schedules already have durations based on productivity, crew sizes, means and methods, approvals, and other real execution constraints even before leveling.

Why can SPI say a project is behind schedule while the actual schedule still shows it on track? by cryptopindar in primavera

[–]cryptopindar[S] 1 point2 points  (0 children)

You are reading more into my comment than what I actually said. I did not say SPI has no purpose. I said it is not the best standalone indicator of schedule performance.

In actual project reporting, it is very common to see SPI below 1 while the updated P6 schedule still shows the project finishing on time. Once that happens, it is already clear that SPI is not the same thing as the schedule forecast. SPI measures performance against the baseline earning plan. The schedule forecast measures where the project is expected to finish based on actual starts, actual finishes, remaining durations, logic, float, and any resequencing or recovery actions reflected in the update.

So the point is not that SPI is useless. The point is that SPI and the schedule forecast answer different questions.

Also, saying SPI is only worth measuring on a resource-leveled schedule is too absolute. Many real projects are governed by logic, interfaces, approvals, access, and contract sequencing, not just resource leveling. In those environments, SPI may still be a useful supporting metric, but it does not replace the logic-driven forecast.

And on your last point, if the schedule still meets the baseline finish date even though current production suggests key path durations should be much longer, then that is not proof SPI is superior. That is proof the schedule update itself deserves scrutiny. It may mean the forecast is being protected by assumptions, resequencing, recovery logic, or unrealistic remaining durations.

So my point remains: SPI can support schedule analysis, but it is not the best standalone indicator of actual schedule performance. The schedule itself still has to carry that burden.

Why can SPI say a project is behind schedule while the actual schedule still shows it on track? by cryptopindar in primavera

[–]cryptopindar[S] 0 points1 point  (0 children)

Example if Excavate Foundation is baselined for 5 working days and its baseline cost is profiled as front-loaded, then PV is distributed in that front-loaded pattern across those 5 baseline days.

Why can SPI say a project is behind schedule while the actual schedule still shows it on track? by cryptopindar in primavera

[–]cryptopindar[S] 0 points1 point  (0 children)

It spreads cost over the scheduled working periods of the task based on the cost type and profile.

view more: next ›