The hottest Agile methodologies Substack posts right now

And their main takeaways
Category
Top Business Topics

Continuous Software Engineering: Part 2 - Continuous Planning & Prioritization

The Healthy Engineering Leader • 19 implied HN points • 19 Sep 24
🕹 Technology Software Engineering Agile methodologies Project management Team Collaboration Continuous Improvement
  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.

Strong Code Ownership

Rethinking Software • 299 implied HN points • 07 Dec 24
🕹 Technology Software Development Agile methodologies Productivity Collaboration
  1. Strong code ownership means a specific developer is responsible for certain sections of code, which helps improve quality and pride in their work.
  2. Just like in the story from Xiaogang, allowing ownership in software can motivate developers and increase productivity.
  3. Some teams might mix strong and collective code ownership to accommodate different personalities and work styles, benefiting everyone involved.

Why Code Authors Should Have the Final Say on Code Reviews

Rethinking Software • 249 implied HN points • 27 Oct 24
🕹 Technology Software Development Code Review Agile methodologies Team Dynamics
  1. Code authors should have the final say in reviews to respect their expertise and autonomy. This helps them feel like true professionals.
  2. Mistakes in code are common and can be fixed quickly, so allowing authors to make decisions helps them learn and improve.
  3. Not all code needs to be perfect from the start, especially in the early stages of projects. Giving authors the control lets them decide how polished their work should be.

Monolithic vs MicroServices.

Software Ninja Handbook • 3 HN points • 12 Sep 24
🕹 Technology Software Development Architecture Cloud Computing System Design Agile methodologies
  1. Monolithic applications have a single codebase, which makes them easier to manage for smaller projects, but harder to debug as they grow. Everything is tightly connected, so a problem in one part can affect the whole system.
  2. Microservices break down applications into smaller, independent services that can be developed and deployed separately. This allows teams to work faster and use different technologies for different parts of the application.
  3. Choosing between monolithic and microservices depends on factors like project size and team structure. Monoliths are good for small projects while microservices are better for larger, complex systems that need flexibility and scalability.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

Ivory towers jeopardize value creation

Ageling on Agile • 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.

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.

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.

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.

Vibes Driven Development: Trust Your Vibes (and ignore everything else)

An Ode to Restlessness • 1 HN point • 26 Jul 24
🕹 Technology Software Development Agile methodologies Creative Process Workplace culture Innovation
  1. Vibes Driven Development (VDD) is all about using your mood and environment to guide your coding. Instead of sticking to strict plans, you let your feelings and instincts shape your work.
  2. To implement VDD, create a cozy workspace, choose music that inspires you, and stay flexible with your coding ideas. Trusting your vibes can lead to unexpected creativity and solutions.
  3. VDD offers a fresh break from traditional methods like Agile and Waterfall, which can feel rigid and stressful. It encourages developers to embrace spontaneity and find their own rhythm while coding.

Revisiting: Why Scrum is the Wrong Way to Build Software Pt.1

Rethinking Software • 1 HN point • 09 Sep 24
🕹 Technology Software Development Agile methodologies Project management Team Dynamics Product Management
  1. Scrum gives all product decision power to the Product Owner, leaving engineers to persuade rather than decide. This can create frustration for engineers who want to contribute to product direction.
  2. Many companies confuse the Product Backlog with engineering tasks, making it hard for engineers to focus on their work without interference. Keeping these backlogs separate can help maintain clear roles.
  3. The way Scrum is often implemented leads to engineers being sidelined in decisions about what to build, showing a need for better practices to include their input in product decisions.

On operations - Leveraging tempo to build software better

Joseph Gefroh • 0 implied HN points • 10 Feb 24
🕹 Technology Software Engineering Agile methodologies Leadership Team Dynamics
  1. Software engineering benefits from cyclical execution in agile methodologies like Scrum, which enable teams to respond to change effectively.
  2. Effective leadership involves setting and managing tempo in cyclical execution, allowing teams to self-synchronize and reduce friction.
  3. To establish an effective tempo, consistency, sustainability, clear starts/stops, and avoiding bleed-over work are key factors to ensure team effectiveness and prevent burnout.