The hottest Team Collaboration Substack posts right now

And their main takeaways
Category
Top Education Topics

10 Situations Where Scrum Is a Burden For Developers

Ageling on Agile • 79 implied HN points • 10 Oct 24
🕹 Technology Team Collaboration
  1. Scrum is not always the best fit for software teams. It works well in complex environments but can become a hassle if the situation is straightforward.
  2. When teams don't need to work together, like in the case of maintenance or support tasks, Scrum can feel unnecessary and unhelpful.
  3. If there’s no proper interaction with stakeholders or a culture of learning, the Scrum framework can hinder progress instead of helping it.

Revenue Operations Pros Are Work Horses

beyondrevenueoperations • 39 implied HN points • 12 Oct 24
💼 Business Team Collaboration
  1. Revenue Operations focuses on aligning sales, marketing, and customer support to boost overall revenue. This means all teams need to work together to improve the customer experience.
  2. Data accuracy and management are crucial in Revenue Operations. Keeping customer data clean helps everyone make better decisions and understand what drives sales.
  3. Ongoing support and training empower teams to succeed. Providing the right tools and resources ensures that all revenue-generating teams can perform at their best.

Continuous Software Engineering: Part 2 - Continuous Planning & Prioritization

The Healthy Engineering Leader • 19 implied HN points • 19 Sep 24
🕹 Technology Team Collaboration
  1. Continuous Planning means regularly updating your plans as things change. This helps teams stay effective and respond quickly to new information.
  2. Continuous Prioritization allows teams to adjust their focus based on what’s most important at any moment. This ensures they always work on tasks that matter the most.
  3. Both continuous planning and prioritization make teams more adaptable. They can shift their strategies easily and keep delivering value, even in changing environments.

Beyond the Code

The Engineering Leader • 59 implied HN points • 15 Sep 24
🕹 Technology Team Collaboration
  1. Top software engineers excel not just in coding but in understanding the bigger picture of their projects. They focus on why they're building something, making sure it meets real needs.
  2. Effective communication and collaboration are key traits of great engineers. They share knowledge with their teams and explain their ideas clearly, making work smoother for everyone.
  3. It's important for engineers to keep learning beyond just coding skills. The best engineers adapt to new challenges, use innovative tools like AI, and think creatively to solve problems.

in-office work > remote work

Tech Ramblings • 19 implied HN points • 07 Sep 24
💼 Business Team Collaboration
  1. In-person work helps teams connect better and communicate more effectively. Many important interactions happen non-verbally, which can be lost in remote settings.
  2. Working in an office allows for quick collaboration and faster problem solving. Teams can discuss ideas and make decisions on the spot, speeding up project timelines.
  3. Remote work may suit experienced professionals or those prioritizing personal life. However, junior developers may benefit more from in-office environments to grow their careers.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

When Overwhelmed, Make a List of Questions

Push to Prod • 39 implied HN points • 05 Aug 24
💼 Business Team Collaboration
  1. When you feel overwhelmed, writing down your questions can help clarify your thoughts. It's a simple way to break down a complex problem.
  2. Answering even one question can give you more confidence and direction, leading to better decision-making. It’s a helpful way to gather information and make progress.
  3. This technique isn't just for work; it can be useful in everyday situations too, like before meetings with accountants or lawyers. Taking the time to write questions helps you feel more prepared.

From Average To Exceptional: 5 Skills To Help You Become The Data Expert Everyone Wants To Work With

SeattleDataGuy’s Newsletter • 494 implied HN points • 19 Feb 25
💼 Business Team Collaboration
  1. Always focus on the real problem behind a request, not just what is being asked. This helps you deliver better solutions that actually meet the business needs.
  2. Using clear frameworks can help organize your thoughts and make complex investigations easier. A structured approach leads to clearer communication and better results.
  3. Keep your communication simple and focused on what matters to your stakeholders. This helps everyone stay on the same page and reduces confusion.

Product Delivery Guide

Untrapping Product Teams • 334 implied HN points • 19 Jul 23
💼 Business Team Collaboration
  1. Product delivery is about creating value steadily, not just following a plan.
  2. Key aspects of product delivery include organizing the product backlog, refining tasks, aligning goals, and delivering value consistently.
  3. Be mindful of common traps like treating the product backlog as a wishlist, separating discovery from delivery, and focusing only on output instead of outcomes.

Re-release: ‘Scrum is an awful project management methodology’

Ageling on Agile • 139 implied HN points • 07 Feb 24
💼 Business Team Collaboration
  1. Consider re-evaluating your project management methodology if it is causing stress and hindering productivity. It is important to adapt and make radical changes when necessary.
  2. Embrace an iterative approach in your product delivery process, especially in unpredictable environments. Small steps, clear goals, and team collaboration can lead to valuable results.
  3. Empower your team by giving them ownership of the backlog, focusing on iteration goals, and encouraging discussions and improvements during demos and retrospectives. Allow flexibility and adaptability in your work processes.

The Analytics Requirements Document

Sarah's Newsletter • 359 implied HN points • 27 Oct 22
💼 Business Team Collaboration
  1. Analytics should be a first-class citizen in crafting product launches to avoid wasted time and ensure measurable success.
  2. Utilize detailed agreements like Product Requirements Documents (PRD) and Analytics Requirements Documents (ARD) to align teams, outline goals, data criteria, assumptions, and finalize expectations.
  3. Involving analytics early in the product evolution lifecycle is crucial for gathering and analyzing data effectively, helping in decision-making, and ensuring alignment across technical and business teams.

Ergodic Development

Software Design: Tidy First? • 883 implied HN points • 25 Aug 23
🕹 Technology Team Collaboration
  1. Ergodicity reminds us to treat systems that continue as is differently from those that fail when changed.
  2. Strategies like reducing irreversibility and having skin in the game can help transform failing systems into sustaining ones.
  3. Load redistribution and encouraging collaboration can make development more survivable and sustainable.

Proposed Addendum to the Manifesto for Agile Software Development

Rethinking Software • 199 implied HN points • 29 Aug 24
🕹 Technology Team Collaboration
  1. Self-management is key for programmers, encouraging them to take charge of their work and make decisions on their own.
  2. Flat organizations are preferred because they promote equality and allow for more collaboration without strict levels of authority.
  3. Direct communication with customers is important, and companies should focus on being transparent and flexible rather than following rigid plans.

Intentionally Building Your Product Stack

Nadia’s Substack • 19 implied HN points • 06 May 24
🕹 Technology 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.

Quality Engineering Basics: Bug Retrospectives

QUALITY BOSS • 39 implied HN points • 05 Feb 24
🕹 Technology Team Collaboration
  1. A Bug Retrospective is a team meeting to review and learn from bugs that occurred during a project. The focus is not on blaming anyone but on understanding why the bugs happened and how to prevent them in the future.
  2. These retrospectives help improve the quality of the product by fostering a culture where everyone takes responsibility for quality. Each bug can be seen as a lesson that can strengthen the team’s processes and test strategies.
  3. To start a Bug Retrospective, gather the team, discuss selected bugs, analyze their root causes, and create an action plan for prevention. Sharing insights and encouraging collaboration can lead to better practices and overall product quality.

Timezone Tricks

Seth’s Substack • 58 implied HN points • 21 Apr 23
💼 Business Team Collaboration
  1. Focus on overlap time for remote teams, not just the timezone difference.
  2. Actively manage how you utilize the limited overlap time for meetings and team activities.
  3. Use recap messages and short recorded videos to enhance communication and collaboration across different time zones.

Breaking the wall between teams

Leading Developers • 100 implied HN points • 22 Oct 24
💼 Business Team Collaboration
  1. Encourage horizontal communication between teams to break down knowledge silos. This can be done through initiatives like Engineering Guilds where team members can share ideas and strategies.
  2. Develop a strong documentation culture to reduce redundancy and ensure important information is easily accessible. Using standardized formats can make documentation simpler and more effective.
  3. Focus on improving onboarding experiences by providing new employees with guides and introductions to other teams. This helps build connections and ensures they have the resources they need from the start.

Advocating for Your Work

The Uncommon Executive • 19 implied HN points • 05 Mar 24
💼 Business Team Collaboration
  1. Advocating for your work is essential for recognition and advancement in your career, especially for women and minorities who may face additional challenges in being acknowledged for their contributions.
  2. Celebrate delivering projects as expected and on time to increase visibility and recognition within the organization, even if you excel at preventing issues before they arise.
  3. Finding different methods to share your achievements like framing them as best practices or thanking collaborators can help in ensuring your wins are seen and appreciated by others.

Communicating To Stakeholders

Become a Senior Engineer • 19 implied HN points • 08 Feb 24
💼 Business Team Collaboration
  1. Identify stakeholders by knowing who they are and understanding their needs.
  2. Tailoring communication involves classifying stakeholders based on their power and interest in the project.
  3. Effective communication with stakeholders requires keeping them satisfied or informed based on their level of power and interest.

Legacy Shmegacy

David Reis on Software • 59 implied HN points • 24 Nov 24
🕹 Technology Team Collaboration
  1. Legacy code often gets that label just because newer programmers don’t understand it. The core issue is usually about people, not the actual code quality.
  2. To avoid creating legacy code, focus on writing clear and simple code that others can easily understand, and engage in practices like mentoring and pair programming.
  3. When dealing with legacy code, try to understand it fully before deciding to rewrite it. Often, working with what's there and improving it gradually is the better choice.

Enemies and Opponents

CPU fun • 242 implied HN points • 07 Mar 23
🎭️ Culture Team Collaboration
  1. Enemies are the people within your own group that you directly compete with for resources.
  2. It is essential to differentiate between opponents and enemies in order to navigate workplace dynamics effectively.
  3. Balancing local and global perspectives can lead to more harmonious and productive collaborations within organizations.

Bi-Weekly Notes

Rethinking Software • 49 implied HN points • 18 Nov 24
🕹 Technology Team Collaboration
  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.

🔐 TPM Microguide: Getting Started With AI Tools For TPM

Building Rome(s) • 11 implied HN points • 03 Jul 25
🕹 Technology Team Collaboration
  1. Start using AI tools gradually in your work. You don't need to be a tech expert; just try small tasks like drafting emails or summarizing updates with chat tools.
  2. Build a supportive community at work by connecting with others interested in AI. Share experiences, tools, and ideas to learn together and create an AI-friendly culture.
  3. Experiment with AI to tackle everyday annoyances. Find small problems at work that automation can solve, which helps you gain confidence and learn how these tools can improve your workflow.

Finalizing design and eye gazing

Splattern • 19 implied HN points • 27 Sep 23
🪑 Design Team Collaboration
  1. Clear communication and a concise agenda improve meeting efficiency. It helps keep discussions on track and reduces confusion among team members.
  2. Maintaining calm and focus is important when facing tight deadlines. Asking the right questions and taking a moment to breathe can lead to more productive conversations.
  3. Building personal connections, like participating in eye gazing, can foster a sense of unity and support, enhancing emotional well-being.

The need for beautiful code

Wednesday Wisdom • 56 implied HN points • 28 Feb 24
🕹 Technology Team Collaboration
  1. Investing time in writing beautiful code is crucial for code longevity and maintainability.
  2. Code that 'mostly works' is not the standard to aim for; focus on creating code that is always functional and meets significant requirements.
  3. Developing a culture of producing beautiful code in a team requires more than guidelines and prizes; it involves a collective shift in mindset and commitment.

How to Build Influence as an Engineering Leader | Kelly Vaughn

Dev Interrupted • 14 implied HN points • 12 Mar 24
💼 Business Team Collaboration
  1. Building influence as an engineering leader requires focusing on trust, communication, and empowerment to succeed in both individual contributor and managerial roles.
  2. Adopting GenAI can be challenging due to the pressure of the hype cycle, and understanding key considerations is crucial for successful implementation.
  3. Having hard deadlines can significantly impact productivity and response rates, highlighting the importance of leveraging deadlines to improve team tempo and cadence.

How to market “marketing” internally

MKT1 Newsletter • 6 implied HN points • 12 Feb 24
💼 Business Team Collaboration
  1. Educating the rest of your company on marketing is crucial for success within a company's marketing team.
  2. Finding common ground with other teams, understanding target audience internally, and recognizing shared goals are key to effective internal marketing.
  3. Setting marketing goals and priorities, sharing them with the company, and establishing a process for handling ad hoc requests are essential for successful marketing outcomes within a company.

The Case for Nitpicking

David Reis on Software • 2 HN points • 18 Feb 24
🕹 Technology Team Collaboration
  1. Nitpicking in code reviews can lead to better code quality and a stronger engineering culture. It's important to discuss style and best practices instead of ignoring them.
  2. Good taste in code exists and is based on collective standards among practitioners. Competent programmers can generally agree on what makes code better, like readability and consistency.
  3. Having a style guide helps streamline code reviews and makes discussions less personal. It sets clear expectations and allows for respectful and constructive feedback.

On-Call Retrospectives

Certo Modo • 0 implied HN points • 01 Feb 23
🕹 Technology Team Collaboration
  1. On-call retrospectives help teams stay connected to the real operational challenges they face and provide insights on how to enhance the on-call experience.
  2. Holding weekly meetings where team members share metrics, experiences, and discuss improvements can lead to a more efficient and enjoyable on-call rotation.
  3. Taking notes during the retrospective and translating them into actionable tasks for improvement can result in smoother on-call shifts and increased team productivity.

Running Successful Engagements

Certo Modo • 0 implied HN points • 28 Mar 23
🕹 Technology Team Collaboration
  1. Identify and maintain a relationship with the team's point of contact to ensure clear communication and accountability.
  2. Prior to starting an engagement, conduct initial discovery to understand the team's operational needs and potential risks.
  3. Create a clear engagement document outlining goals, expectations, and metrics for success, ensuring alignment with the team's objectives.