The hottest Agile Substack posts right now

And their main takeaways
Category
Top Technology Topics

9 Things Product Owners Should Stop Doing

Ageling on Agile • 99 implied HN points • 27 Oct 24
💼 Business Management Agile Productivity Development Leadership
  1. Product Owners shouldn’t act like team managers. They should focus on the product goals and let Developers decide how to achieve them.
  2. It's important for Product Owners to be part of the team. They should engage with the Developers regularly and not just during official meetings.
  3. Product Owners need to avoid over-managing the details of tasks. They should trust Developers to find the best ways to reach the goals set for the product.

10 Things People Don't Realize About Scrum

Ageling on Agile • 119 implied HN points • 20 Oct 24
💼 Business Agile Management Leadership Training
  1. Scrum isn't just about short-term goals; it focuses on the long-term vision for the product. The Product Owner plays a key role in setting a clear Product Goal and regularly reviews progress.
  2. The purpose of a Sprint is to learn and adapt, not just to deliver a set amount of work. Each Sprint acts as a learning cycle where teams reflect and plan the next steps based on what they've achieved and learned.
  3. The Scrum Master is more than just a facilitator; they are also responsible for helping the whole organization adopt Scrum effectively. They guide both the team and other stakeholders to understand their roles in the process.

7 Estimation blunders

Ageling on Agile • 39 implied HN points • 24 Oct 24
💼 Business Management Agile Software Teamwork Estimation
  1. Estimating work is hard, especially for complex tasks. It's okay to acknowledge that some work can't be easily estimated and to focus on learning instead.
  2. Teams often have different opinions on estimates, which can lead to valuable discussions. These conversations help everyone align on the work and understand each other's perspectives.
  3. Estimates shouldn't be treated as strict commitments. If people outside the team are pushing for deadlines based on estimates, it's important to push back and clarify that estimates are just rough calculations.

Scrum Is No Excuse To Avoid Accountabilities

Ageling on Agile • 99 implied HN points • 03 Oct 24
💼 Business Management Agile Productivity Teamwork
  1. Scrum helps teams work better, but it doesn't mean people can ignore their responsibilities. Everyone needs to step up and be accountable.
  2. Self-management in Scrum isn't just about freedoms; it also includes taking on duties and being responsible for their work.
  3. It's important for everyone in a Scrum team to communicate clearly and understand what is needed to succeed, especially regarding project timelines.

One-on-one coaching moment for paid subscribers

Ageling on Agile • 39 implied HN points • 09 Oct 24
💼 Business Coaching Management Leadership Agile Product
  1. One-on-one coaching sessions are available for paid subscribers. These sessions allow for personal engagement on topics like Agile, Product Management, and Leadership.
  2. Each subscriber can have six half-hour coaching moments a year. These moments can help clarify work-related issues and provide guidance.
  3. Feedback from subscribers shows that the coaching is valuable. Many find the insights helpful for understanding their challenges and finding solutions.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Join The Book Club in September: Implementing Lean Software Development

🔮 Crafting Tech Teams • 99 implied HN points • 24 Aug 23
🚌 Education Software Development Book Club Agile
  1. Join the book club challenge in September to learn about implementing Lean Software Development.
  2. Participate in discussions to apply lean and lowercase-A agile principles with your team and improve speed reading skills.
  3. Start with a 7-day free trial to access the full post archives and engage in impactful learning as soon as possible.

New Generation Product Leader Model

Product Power by Samet Ozkale • 98 implied HN points • 16 Feb 23
💼 Business Product Management Data-driven Agile Collaboration
  1. Product leaders should focus on data-driven and customer-centric approach in product development.
  2. Understanding the user through research and user feedback is crucial for making informed decisions and solving real problems.
  3. Cross-functional collaboration and transparent accountability are essential for fostering innovation and delivering results in product management.

The Blurred Line Between Methodology and Framework

Building Rome(s) • 13 implied HN points • 24 Aug 23
🕹 Technology Methodology Framework Software Development Agile Project management
  1. The role of a Technical Program Manager (TPM) involves defining and implementing the methodology and framework for software development projects.
  2. Methodologies provide general principles while frameworks offer specific plans of action.
  3. It's important for TPMs to be flexible in choosing the right methodology and framework based on the project's specific needs and requirements.

23/36 : 📚 A Guide to Effective User Stories and Story Mapping and Pointing

Product Mindset's Newsletter • 13 implied HN points • 02 Jul 23
🕹 Technology Estimation Agile
  1. User stories are informal explanations of software features from an end-user perspective.
  2. Creating user stories keeps the team focused on real users, encourages collaboration, and drives creative solutions.
  3. Story splitting is important to break down large user stories into smaller, valuable increments that can be completed within a sprint.

Can You Hear the Pain?

Rethinking Software • 2 HN points • 14 Aug 24
🕹 Technology Software Development Agile Management Engineering
  1. Many developers are unhappy with Agile and Scrum. They feel it leads to more stress and micromanagement instead of helping them.
  2. There's a strong desire among developers for more autonomy in their work. They want to solve problems themselves rather than follow strict daily tasks.
  3. People are questioning the effectiveness of Agile methods. If developers are not thriving under these processes, it might be time for a change.

The First Scrum...

Rethinking Software • 1 HN point • 30 Sep 24
🕹 Technology Software Development Agile Productivity Innovation
  1. Scrum is an approach used to make teamwork more effective. It helps teams focus on delivering results in small, manageable pieces.
  2. Good communication is essential in Scrum. Regular check-ins and updates keep everyone on the same page and help solve problems quickly.
  3. Scrum encourages continuous improvement. Teams should always look for ways to do better and learn from past experiences.

Bi-Weekly Notes

Rethinking Software • 0 implied HN points • 05 Nov 24
🕹 Technology Software Agile Work Culture Programming Productivity
  1. Reaching consensus in teams can be difficult, often leading to tension. It's better to allow differing opinions and find a way to move forward, rather than forcing everyone to agree.
  2. Many workers are stuck using tools like Microsoft Teams, which can be frustrating for coders. It raises the question of whether companies are prioritizing cost savings over better options, like Slack or Discord.
  3. There's a concern about the 'Agile Industrial Complex' imposing rigid processes on developers. It's important to remember that agile methods should be flexible and designed based on the team's needs, not forced upon them.

Should you set ambitious or easy goals?

Kartick’s Blog • 0 implied HN points • 06 Dec 24
💼 Business Goal setting Psychology Commitment Agile Productivity
  1. Your mindset matters when setting goals. Some people need big goals to feel motivated, while others might feel stressed by them.
  2. Deadlines can affect your choice of goals. If you're short on time, a small goal is often better than trying to rush a bigger one.
  3. You can combine easy and ambitious goals. For example, do a push-up today and plan to play tennis tomorrow. It's okay to mix them!

Three Things to Change Exercise: A Different Kind of Retrospective

QUALITY BOSS • 0 implied HN points • 28 Feb 24
💼 Business Leadership Teamwork Communication Management Agile
  1. Encourage your team to suggest three changes they want to see. This helps everyone share their ideas on what could improve the team's work environment.
  2. Once you gather suggestions, look for common themes and discuss them as a group. This makes it easier to find important issues to focus on.
  3. After identifying top changes, involve the team in brainstorming ways to implement them. Working together on solutions strengthens teamwork and leads to better outcomes.

🐿️ Decision Point, Montana - The Insanely Profitable Tech Newsletter

Squirrel Squadron Substack • 0 implied HN points • 17 Dec 24
🕹 Technology Software Innovation Leadership Experiments Agile
  1. Lewis and Clark faced a tough choice during their expedition and used small experiments to gather information before deciding which route to take. This shows the importance of testing different options when faced with uncertainty.
  2. In tech, instead of following rigid rules or 'best practices', teams should be flexible and adapt quickly. Fast iterations and feedback from customers are key to navigating complex projects.
  3. It's essential to create a safe environment where team members can learn from their mistakes. Viewing failed experiments as learning opportunities helps drive innovation and growth.

Shape your team to be a profit centre

🔮 Crafting Tech Teams • 0 implied HN points • 27 Jun 23
💼 Business Team Management Economics Agile
  1. Teams can be shaped to focus on increasing profit targets, rather than just reducing costs.
  2. Utilizing Tactical Agility by feature slicing across fully functional verticals can help increase profit targets for high performing teams.
  3. Understanding the subtle and unintuitive economics of Agile can help in shaping teams to be more effective profit centres.