Ageling on Agile

Ageling on Agile explores the facets of Agile methodologies, value creation, and leadership within modern organizations. It critiques and offers advice on Agile frameworks like SAFe and Scrum, discusses the roles and growth paths in Agile careers, and emphasizes the importance of organizational culture and team dynamics for successful Agile implementation.

Agile Methodologies Value Creation Organizational Leadership Product Management Team Dynamics Career Development in Agile Organizational Culture

The hottest Substack posts of Ageling on Agile

And their main takeaways

The most neglected words of the Agile Manifesto

119 implied HN points • 31 Oct 24
🕹 Technology Software Development Agile Methodology Process Improvement Collaboration Project management
  1. The Agile Manifesto emphasizes that we're always discovering better ways to develop software, not just relying on established methods. It's about improving and adapting continuously.
  2. Though there are popular Agile methods like Scrum and XP, the key is to find what works best for your unique organization. Every team is different, and a one-size-fits-all approach may not fit your needs.
  3. The first sentence of the Agile Manifesto is often overlooked, but it encourages ongoing exploration in software development. This mindset fosters innovation and flexibility rather than strict adherence to any single method.

9 Things Product Owners Should Stop Doing

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

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.

5 Ways Agile Coaches Undermine Agility

159 implied HN points • 13 Oct 24
💼 Business Management Agile Methodology Coaching Organizational Culture Team Dynamics
  1. Agile is not a goal; it's a tool to achieve bigger goals like better teamwork and faster delivery. Coaches should focus on the benefits of Agile instead of just promoting the process itself.
  2. Some Agile Coaches act like salespeople, pushing their one-size-fits-all solution instead of customizing their approach to meet each organization's unique needs. Good coaches listen to what the company really needs first.
  3. Many Agile Coaches focus only on the teams without considering the rest of the organization. Everyone needs to understand how Agile impacts their work to truly benefit from it.

7 Estimation blunders

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.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

The most neglected words of the Agile Manifesto

99 implied HN points • 17 Oct 24
🕹 Technology Software Development Agile Methodology Project management Innovation Best Practices
  1. The Agile Manifesto emphasizes that we are constantly discovering better ways to develop software, not just using established methods. This means we should keep looking for improvements in our processes.
  2. It's important to focus on finding unique solutions that work for your specific organization. No single method is perfect for everyone.
  3. The Agile principles encourage collaboration and adaptation rather than strictly following a set plan. Being flexible helps teams create more value.

10 Situations Where Scrum Is a Burden For Developers

79 implied HN points • 10 Oct 24
🕹 Technology Software Development Agile Methodology Project management Team Collaboration Product Management
  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.

Scrum Is No Excuse To Avoid Accountabilities

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

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.

Are you recently promoted to a Product Manager position? - Here are a few pitfalls to avoid

219 implied HN points • 14 Jan 24
💼 Business Management Skills Learning Hierarchy Challenges
  1. The role of a product manager is different from roles like project manager, engineer, or business analyst.
  2. Newly promoted product managers should avoid the Dunning-Kruger effect by continuously learning and challenging themselves.
  3. Recognizing the Peter Principle is essential - not everyone is suited to be a product manager, and self-awareness is key.

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

139 implied HN points • 07 Feb 24
💼 Business Management Product Development Team Collaboration Workplace culture Process Improvement
  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.

Beware of Scaled Agile

99 implied HN points • 24 Jan 24
💼 Business Agile Scaling Startup
  1. You don't need all the complexities of Agile scaling approaches to solve your issues.
  2. Start small and gradually add complexity based on your real needs.
  3. Focus on nailing the solution before trying to scale it.

8 Ways Organizational Culture Kills Agility

79 implied HN points • 11 Feb 24
💼 Business Organizational Culture Agility Management Teamwork
  1. Implementing Agile in an organization goes beyond just claiming to be Agile; it requires a cultural shift.
  2. Having a hierarchical structure, lack of learning culture, and siloed responsibilities can hinder an organization's agility.
  3. Organizations valuing output over outcome, prioritizing individual efficiency, and fostering HIPPO culture undermine Agile principles and hinder effectiveness.

SAFe Scrum - Is it actually Scrum?

259 implied HN points • 26 Mar 23
🕹 Technology Agile Development Frameworks
  1. SAFe 6.0 has replaced ScrumXP with SAFe Scrum for Agile Teams in the Scaled Agile Framework.
  2. The post questions how closely SAFe Scrum aligns with the principles outlined in the Scrum Guide.
  3. The author suggests that ScrumXP did not meet the qualifications of being recognized as Scrum.

Ivory towers jeopardize value creation

59 implied HN points • 04 Feb 24
💼 Business Management Collaboration Value Creation Organizational Culture Agile methodologies
  1. Ivory towers in organizations can create conflict and hinder collaboration between teams with different objectives.
  2. To foster value creation, it's essential for individuals in leadership positions to step down from ivory towers and actively collaborate with all stakeholders.
  3. Blocking the learning loop by maintaining ivory towers can lead to wasted time, effort, and money, hindering the organization's ability to adapt in a fast-changing world.

Don't commit to the Sprint Backlog

159 implied HN points • 14 Jun 23
💼 Business Project management
  1. Don't view the Sprint Backlog as a commitment with high stakes.
  2. Problems can arise when items in the Sprint Backlog are not completed.
  3. Avoid increased stress levels and overtime by not treating Sprint Backlog as a strict commitment.

12 great ways to fail with Agile

159 implied HN points • 29 Mar 23
💼 Business Agile
  1. Focus on value, not just on velocity.
  2. Understand and adhere to the Agile principles for success.
  3. Measure success by the value delivered, not just by the speed of delivery.

10 Product Owner mistakes

139 implied HN points • 08 Mar 23
💼 Business Product Management
  1. Product Owners need to take ownership to succeed in their role.
  2. Product Owners should not say 'Yes' to everything to maximize product value.
  3. Product Owners should be able to adapt and update the product backlog to meet goals.