The hottest Project management Substack posts right now

And their main takeaways
Category
Top Technology Topics

No sacred masterpieces

Basta’s Notes • 753 HN points • 15 Sep 23
🕹 Technology Software Development Data science Engineering Project management Web Development
  1. Sometimes, valuable projects end abruptly without much recognition or lasting impact.
  2. It's important to focus on creating business value with your work, rather than building impressive but ultimately unnecessary solutions.
  3. Every piece of code you write as an engineer is legacy and may not last forever, so focus on learning from each project's outcome.

Beyond Guesswork: The Art and Science of Project Estimation

Mindful Matrix • 179 implied HN points • 08 Feb 24
💼 Business Project management Software Engineering Estimation Risk Analysis Communication
  1. Project estimation is a critical skill influencing project success; it involves setting realistic expectations, aligning efforts, and managing resources effectively.
  2. Key considerations in estimation include understanding project scope, conducting risk analysis, and utilizing estimation strategies like historical analysis and buffer times.
  3. Transparency and communication are crucial in estimation; transparency helps manage stakeholder expectations while effective communication ensures clarity and trust in the estimation process.

Is your project on schedule? How do you know?

Respectful Leadership • 54 implied HN points • 29 Dec 24
💼 Business Project management Leadership Team Dynamics Risk management
  1. To keep projects on track, it's essential to dig deep into details and understand all aspects involved. This helps find hidden issues before they become problems.
  2. Unexpected challenges will always arise, so having backup plans is crucial. It's better to prepare for potential setbacks than to face surprises later.
  3. Effective project estimates need thorough discussions and clear communication among all teams. This helps ensure everyone understands what needs to be done and avoids over-optimism.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Is the grass greener on the consulting side?

Kenny’s Sub • 119 implied HN points • 27 Dec 23
💼 Business Consulting Entrepreneurship Freelancing Project management Work-life balance
  1. Jumping into freelancing or consulting can seem better, but it often comes with its own challenges. It's important to realize that every choice has its problems.
  2. Finding the right work-life balance is key. It's okay to take breaks from things you do regularly to avoid burnout.
  3. When choosing what to work on, ask yourself what problems you're willing to tackle. Not every job will be perfect, and it's vital to focus on what truly motivates you.

Becoming a Data Engineering Force Multiplier

SeattleDataGuy’s Newsletter • 671 implied HN points • 23 Apr 23
🕹 Technology Data Engineering Skills Project management Communication Resources
  1. Data engineering is crucial in today's data-driven landscape, with a growing demand for skilled professionals.
  2. Developing technical skills like architecture, data modeling, coding, testing, and CI/CD is essential for becoming a successful data engineer.
  3. Non-technical skills such as teaching, long-term project planning, and communication are equally important for data engineers to excel and become force multipliers.

Reader Mailbag: Architect having a hard time letting go

Tech and Tea • 82 implied HN points • 27 Oct 24
🕹 Technology Software Development Team Management Project management Collaboration
  1. Building a good relationship with your architect is important. Showing that you appreciate his work can help create a positive atmosphere.
  2. Understanding why the architect is holding on too tightly to tasks can help you address his concerns. It might be about trust, feeling needed, or being overwhelmed.
  3. Start with small projects to help him delegate tasks. This can build trust and reduce his workload, allowing him to focus on more strategic aspects.

Unicorn Projects

Polymathic Being • 65 implied HN points • 01 Dec 24
💼 Business Innovation Project management Process Optimization Systems Thinking Best Practices
  1. Many teams believe their projects are special or unique, but this mindset can lead to mistakes because they ignore proven methods that could help them succeed.
  2. Looking for what’s common between projects instead of focusing on differences can help teams use best practices more effectively, leading to better outcomes.
  3. True innovation happens when teams recognize common problems and find areas that actually need new solutions, rather than chasing after the idea of uniqueness.

Five Lessons from Walmart's Innovative Approach to Network Design

Mike Talks AI • 157 implied HN points • 09 May 23
💼 Business Supply Chain Innovation Visualization Project management
  1. Walmart's innovative approach to network design involved building a second model for transition planning.
  2. Linking strategic design to load planning and using simulation for execution is crucial in network design.
  3. Visualization is important in gaining approval and support for large-scale network design projects.

Bi-Weekly Notes

Rethinking Software • 49 implied HN points • 18 Nov 24
🕹 Technology Software Development Agile Methodology Team Collaboration Project management
  1. Agile is all about being flexible and responding to changes quickly, rather than trying to predict everything in advance. It helps teams deal with unexpected challenges effectively.
  2. Good teamwork means collaborating and helping each other out. If you get stuck on a project, it’s important to ask your teammates for support instead of trying to figure everything out alone.
  3. Building software is unpredictable, so it’s best not to set strict deadlines and feature lists. Trying to rush or add more people won't necessarily speed things up, and can often make things worse.

Engineering Managers Should Not Exist

Victor’s Substack • 41 HN points • 26 Mar 24
🕹 Technology Management Software Engineering Project management HR Consulting
  1. Software engineering managers should not exist as they generally take on multiple roles poorly, whereas specialists could excel at each task.
  2. Engineering managers often were mediocre engineers who compensated by picking up non-engineering tasks and ended up in managerial roles.
  3. Best teams often function well without an engineering manager observing their every move, allowing engineers to focus and be more productive.

Why is there more than one way to end a while loop?

Mostly Python • 419 implied HN points • 14 Mar 23
🕹 Technology Programming Python Software Development Project management
  1. Programming languages may offer multiple ways to accomplish the same task for different use cases.
  2. Python emphasizes having one clear and obvious way to do things to promote readability and maintainability.
  3. Ending a while loop in Python can be done using the while statement, break statement, or a flag - each with its own unique advantages.

Console #172 - Interview with Dima of Novu - open-source notification infrastructure

Console • 354 implied HN points • 27 Aug 23
🕹 Technology Open Source Software Development Project management Collaboration
  1. Novu is an open-source notification infrastructure created by Dima and his co-founder to simplify communication for businesses.
  2. Novu empowers users to switch between email or SMS delivery providers seamlessly with its core principles of Triggers, Workflows, and Providers.
  3. Novu has a diverse team from around the world, emphasizes self-hosting, and offers a managed cloud version and enterprise licenses for revenue.

3 steps to value focused data product management

Datent • 58 implied HN points • 09 Feb 24
💼 Business Data Management Product Development Project management Innovation
  1. Transitioning from a BI role to a data product team requires defining a Value Gateway to ensure projects deliver tangible benefits.
  2. To manage the progress and accountability of data work, reporting on value at key points is crucial, showcasing the value realized and areas needing support.
  3. Establishing a process around failing fast and doubling down on successful projects, supported by agile project management, is essential for efficient data product management.

Technical Debt 101: A Short Quick Guide

Weekend Developer • 19 implied HN points • 31 May 24
🕹 Technology Software Development Code Quality Project management Testing
  1. Technical debt is like borrowing time when you write code shortcuts that need to be revised later, similar to financial debt repayment with interest.
  2. Ways technical debt can occur: rushed development, lack of documentation, poor testing, ignoring refactoring, avoiding version upgrades, and lacking developer tools.
  3. Consequences of excessive technical debt include decreased productivity, increased bugs, higher costs, team morale issues, and security risks; managing it involves prioritizing refactoring, writing tests, documenting, reviewing code, and communicating with stakeholders.

Scrum is the Symptom, not the Problem

Rethinking Software • 77 HN points • 07 Aug 24
🕹 Technology Software Development Corporate Governance Agile Methodology Project management Engineering Culture
  1. Scrum is often seen as a bad tool for management, restricting developers' productivity and self-esteem. Many developers feel frustrated, yet companies keep using it because it controls people rather than empowers them.
  2. The main issue isn't Scrum itself, but a bigger problem of control in software companies. Developers often lack genuine power and are seen more as replaceable parts than valuable contributors.
  3. To truly change their working conditions, developers may need to start their own companies or work independently. This way, they can reclaim decision-making power and avoid micromanagement.

How to Measure Progress in a Software Project

Rethinking Software • 56 HN points • 19 Sep 24
🕹 Technology Software Development Agile Methodology Project management
  1. The main way to measure progress in a software project is by assessing the working software itself, not through estimates or projections. This means focusing on what you can actually deliver and test at any moment.
  2. Agile encourages regular feedback by delivering small increments of software frequently, allowing teams to adjust based on customer needs. This approach helps avoid wasting time on unnecessary features.
  3. Many teams have reverted to old methods of measuring progress with estimates and projections, which can lead to project failures. Sticking to the core Agile principle of valuing actual working software is crucial.

Think Slow, Act Fast

burkhardstubert • 99 implied HN points • 08 Sep 23
🕹 Technology Software Development Project management Architecture Agile methodologies Continuous Delivery
  1. Thinking slowly helps you plan better before jumping into action on projects. It's important to take the time to think through complexities and potential issues.
  2. Projects often fail when teams rush into coding without adequate planning. This can lead to messy products that are hard to maintain and costly to fix.
  3. Effective planning should involve experimentation and iteration, similar to how Pixar develops movies. This approach helps to refine ideas early and reduce risks down the line.

The MANY Alternatives to Scrum

Rethinking Software • 50 HN points • 01 Oct 24
🕹 Technology Software Development Agile methodologies Project management Open Source Team Dynamics
  1. Scrum isn't the only way to manage software development. There are many effective alternatives that some companies are using successfully.
  2. Each alternative relies on worker freedom and experimenting, so it's important to find a process that fits your team's needs, not just a one-size-fits-all solution.
  3. Processes like Kanban or Agile focus on continuous flow and autonomy, which can lead to better results than traditional Scrum methods.

Intentionally Building Your Product Stack

Nadia’s Substack • 19 implied HN points • 06 May 24
🕹 Technology Product Management Software Development AI Project management Team Collaboration
  1. When setting up your technology stack, choose tools that best serve both your product and team.
  2. As AI becomes more prevalent in software development, product managers and founders need to adapt their product stacks.
  3. Regularly update and tailor your product stack based on your team's needs, growth, and the evolving technology landscape.

How TPMs Lose Credibility and What to Avoid

Building Rome(s) • 20 implied HN points • 14 Jan 25
💼 Business Management Leadership Project management Team Dynamics Communication
  1. Credibility is crucial for TPMs because it's how they build trust with their teams and leaders. Consistently following through on promises and communicating effectively helps maintain that trust.
  2. Small mistakes can lead to big problems. Overlooking details, not following processes, and poorly communicating can damage a TPM's credibility quickly.
  3. Being proactive rather than reactive is important. TPMs should anticipate potential issues to show they're engaged and capable, which strengthens their credibility.

My biggest leadership failure (so far)

Boots Too Big • 17 HN points • 15 May 24
💼 Business Leadership Failure Career growth Project management Self-reflection
  1. Feeling lost in a new leadership role is common, especially when transitioning from a different position with mismatched skills.
  2. Leadership roles require different tools such as clear communication, flexibility in technical design, and proper ownership of gaps.
  3. Learning from mistakes is crucial for growth in leadership positions, and self-reflection through journaling can help in being prepared for future challenges.

The "Macros" for healthy engineering teams - part 2: Proteins

The Healthy Engineering Leader • 19 implied HN points • 02 Apr 24
💼 Business Team Management Leadership skills Continuous Improvement Project management Communication Skills
  1. Continuous improvement is like protein for engineering teams. Just as proteins help our bodies grow and heal, ongoing learning helps teams adapt and stay strong.
  2. Team skills are essential for a resilient team. Skills like project management and communication are the building blocks that help a team work well together and tackle challenges.
  3. Engineering leaders play a key role in developing these skills and fostering a culture of improvement. By supporting their team's growth, leaders create an environment where everyone can thrive.

The Daily Scrum

Rethinking Software • 29 HN points • 25 Sep 24
🕹 Technology Software Development Project management Agile methodologies Team Dynamics Workplace culture
  1. Daily Scrum meetings can feel like micromanagement and add stress to developers. It often makes people feel pressured to justify their productivity.
  2. Development work is not always linear, and sometimes progress takes time. It’s okay if some days don’t yield immediate results.
  3. Scrum's requirement for daily check-ins suggests a lack of trust in developers. It would be better if teams could choose when and how to meet, respecting their autonomy.

Rethinking The Software Development Life Cycle

Beekey’s Substack • 2 HN points • 31 Jul 24
🕹 Technology Software Development Agile Methodology Project management User Experience
  1. The traditional waterfall model of software development rarely works well. Projects often go over budget, and the software can end up being unusable.
  2. Agile development was created to improve this, but many teams still stick to outdated processes and struggle with meeting user needs.
  3. Involving users early by writing code during requirements gathering can lead to better feedback and faster development, making sure the software created is valuable.

Fit then optimize

Sunday Letters • 159 implied HN points • 10 Apr 22
🕹 Technology Software Optimization Project management Engineering Product Development
  1. Always focus on finding the right fit for your project before trying to optimize it. It’s easier to make improvements once you know what works.
  2. Watch out for a messy situation where too many things need fixing. Start cleaning up gradually once you see your project gaining traction.
  3. Avoid creating overly complex systems before you understand the problem you're solving. Keep things simple and relevant to ensure usefulness.

Zenful Estimates: Ditching Task Estimates to Build a Faster Team

Dev Interrupted • 51 implied HN points • 14 Mar 24
🕹 Technology Software Engineering Project management Agile methodologies Engineering Culture
  1. Engineering task estimates are often costly in time and resources, leading to inaccuracies and increased stress within the team.
  2. Distinguishing between task estimation and project estimation can help teams prioritize better and allocate resources more effectively.
  3. By adopting a 'Zenful' approach that focuses on project estimates rather than granular task estimates, teams can save time, reduce stress, and improve overall efficiency.

How to beat the critical path

Wednesday Wisdom • 47 implied HN points • 13 Mar 24
🕹 Technology Software Engineering Project management Planning
  1. To beat the critical path, the first step is to acknowledge its existence.
  2. Effective project planning, like utilizing the Critical Path Method (CPM), can prevent delays and ensure timely project completion.
  3. Maintaining a Directed Acyclic Graph of project activities with expected durations is crucial in project management to identify critical paths and manage dependencies effectively.

The rainbow of disgust and joy

Sunday Letters • 119 implied HN points • 15 May 22
🕹 Technology Software Development Coding Project management Product Design
  1. When working on code, it's common to feel frustrated with the design. It's important to remember that things often need to move quickly to stay competitive.
  2. Finding a balance between speed and maintaining good code is key. Being too perfect can be as problematic as moving too fast.
  3. Emotions about your code can help gauge your progress. Being slightly embarrassed yet moving fast usually leads to better outcomes.

Why "bias for action" is not good enough

The Caring Techie Newsletter • 11 implied HN points • 12 Nov 24
🕹 Technology Software Engineering Project management Leadership Decision-making Risk management
  1. Having a 'bias for action' can be good, but it's not always the right approach. Sometimes, acting without enough thought can lead to bigger problems.
  2. In situations where you don't fully understand the problem, it might be better to wait and gather more information before jumping to conclusions.
  3. Instead of rushing into decisions, take a moment to think things through. Thoughtful action can help you make better choices.

How to run your marketing team day-to-day

MKT1 Newsletter • 5 implied HN points • 16 Jan 25
💼 Business Marketing Strategic Planning Goal setting Team Dynamics Project management
  1. Break your big goals into smaller monthly tasks. This helps everyone see what they need to do each month to stay on track.
  2. Set regular meetings for your team to talk about important topics and updates. Make sure these meetings have a purpose and keep everyone aligned.
  3. Connect daily tasks to your overall goals. This means making sure every project and request relates back to what you are trying to achieve.

Breakdown: Monday.com's AI Credit Model

Good Better Best • 3 implied HN points • 14 Feb 25
💼 Business SaaS Pricing AI Project management Automation
  1. Monday.com has introduced an AI credit model that charges users based on successful tasks completed by AI. This encourages teams to try out AI features without fear of wasting credits.
  2. The AI features include automations, dynamic data processors, templates, and specialized assistant apps, all aimed at making workflows more efficient and productive.
  3. This credit-based pricing model allows for flexibility and predictability in costs, but can also add complexity that companies must manage.

The Fight Begins

Splattern • 19 implied HN points • 14 Sep 23
💼 Business Work Culture Career development Project management Networking
  1. The person has chosen to take on a challenging project at work instead of accepting a severance package. They see it as a chance to learn and grow.
  2. Feedback from both their boss and a senior engineer highlighted areas for improvement, making them realize they need to change their approach to work and learning.
  3. They are making a conscious effort to balance work and life, treating this project like a marathon where pacing and focus will help them succeed.