The hottest Agile Methodology Substack posts right now

And their main takeaways
Category
Top Technology Topics

The most neglected words of the Agile Manifesto

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

Tidy First Example

Software Design: Tidy First? • 463 implied HN points • 30 Jan 25
🕹 Technology Software Design Programming Development User Experience Agile Methodology
  1. It's important to make hard changes easier before tackling them. This means breaking down tough tasks into simpler steps.
  2. Many people want to make the easy changes they envision, but they often overlook the complexity involved.
  3. Always pay attention to examples in learning; they can provide valuable insights that you might miss if you skim over them.

5 Ways Agile Coaches Undermine Agility

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

The most neglected words of the Agile Manifesto

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

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

The value of grunge work

Wednesday Wisdom • 113 implied HN points • 15 Jan 25
🕹 Technology Software Development Agile Methodology Tech Debt Work Culture Engineering Practices
  1. Tech debt happens when we make bad decisions in software development. It can pile up, making fixing problems a big task for teams.
  2. Doing hands-on work, or 'grunge work,' helps deepen understanding of the tech systems. It’s crucial for maintaining and improving technology.
  3. To tackle tech debt effectively, it should be part of official job expectations. This way, everyone contributes and helps keep things running smoothly.

I Was Wrong About Scrum, Again

Rethinking Software • 549 implied HN points • 30 Nov 24
🕹 Technology Software Development Agile Methodology Project management Team Dynamics Product Management
  1. Sprints can feel non-stop and stressful since they don't have breaks, which can lead to burnout. It's suggested that a 'sustainable pace' would help, but taking real breaks might be a simpler solution.
  2. Daily stand-ups can make team members feel pressured to justify their work constantly. However, the intent behind them is not for status updates but to facilitate communication and support.
  3. The role of a Product Owner in Scrum can leave developers feeling sidelined. Developers may worry that their insights are overlooked, but it’s believed that good Product Owners will always prioritize the development team's needs.

Scrum’s Definition of Done Is Polishing Plates in a Burning Kitchen

Rethinking Software • 499 implied HN points • 20 Nov 24
🕹 Technology Software Development Agile Methodology Project management Quality Assurance Team Dynamics
  1. Scrum's Definition of Done creates extra pressure on developers to deliver perfect work, even when the process is chaotic. It doesn't fix the problems; it just shifts the blame onto the team.
  2. Instead of focusing on quality, Scrum encourages speed and follows strict checklists. This leads to developers cutting corners just to meet unrealistic deadlines.
  3. Real improvements would come from changing the whole process, like allowing more time for reflection, empowering developers, and reducing unnecessary meetings, which would promote better quality work.

Operation Liberate Programmer

Rethinking Software • 399 implied HN points • 05 Dec 24
🕹 Technology Software Development Artificial Intelligence Freelancing Agile Methodology
  1. Scrum and its new version, Extreme Agile, focus too much on speed without considering the quality of work. This prioritization can lead to worsening job conditions for programmers.
  2. Programmers have the option to explore freelancing or starting their own businesses, especially with AI tools making it easier. This could provide more freedom and control over their work.
  3. Instead of waiting for companies to change, programmers should take action to create their own opportunities, sharing their experiences and insights to help others along the way.

Why sprints are taking the joy out of building software

Leading Developers • 147 implied HN points • 29 Oct 24
🕹 Technology Software Development Agile Methodology Product Management Team Dynamics Engineering Practices
  1. Sprints can make software development feel rushed and stressful. Teams often end up prioritizing completing tasks over enjoying the process of creating.
  2. Agile isn't just about following the sprint process; it's more about flexibility and responding to change. Focusing too much on the sprint leads to sticking to the rules instead of adapting to needs.
  3. Instead of traditional sprints, teams might benefit from cycles where they take their time, release when ready, and allow some room for creativity and quality work. This can create a more enjoyable work environment.

Definition of Dumb

Rethinking Software • 249 implied HN points • 30 Nov 24
🕹 Technology Software Development Agile Methodology Project management Quality Assurance Team Dynamics
  1. The Definition of Done in Scrum can often mask real problems instead of solving them. It makes it seem like poor quality doesn't exist by placing all responsibility on the developers.
  2. Many companies stick to strict processes without recognizing their flaws. This leads to frustration among developers who are pushed to meet unrealistic expectations.
  3. Empowering developers to create their own processes might lead to better results. By trusting the team, companies can produce high-quality work without getting bogged down by rigid frameworks.

Why Scrum is Stressing You Out

Rethinking Software • 445 HN points • 11 Sep 24
🕹 Technology Software Development Agile Methodology Productivity Project management
  1. Sprints make work feel never-ending because they are constant deadlines without breaks. Unlike past methods, there’s no time to rest and recharge, leading to ongoing stress.
  2. Sprints are often imposed on teams without their input, removing their freedom and motivation. Control over how work is done is important for reducing stress and improving satisfaction.
  3. In Scrum, there is little time for preparation before starting tasks. Developers need time to think, plan, and get ready to tackle projects, or they end up feeling overwhelmed and unprepared.

Code Reviews, Not Code Approvals

Rethinking Software • 299 implied HN points • 03 Nov 24
🕹 Technology Software Development Remote work Project management Code Review Agile Methodology
  1. Asynchronous communication is key for remote work, allowing people to respond when they can without blocking others. This way, everyone can keep working on their own tasks without unnecessary interruptions.
  2. Traditional code reviews often act more like approvals, which can slow down progress and cause delays. It's better to think of them as a way to give feedback after code is deployed, not as a gatekeeping step.
  3. By changing code reviews to be more like reviews after deployment, teams can keep moving forward. This helps avoid bottlenecks and allows for quicker corrections and improvements in code.

How Agile Are You Really?

Rethinking Software • 299 implied HN points • 11 Oct 24
🕹 Technology Software Development Agile Methodology Project management Organizational Behavior
  1. Agile should give more decision-making power to developers instead of keeping it all with managers. When developers can make choices, they can respond better to challenges in their work.
  2. Developers should connect directly with customers instead of relying on a middle person, like a product owner. This helps them understand what users want and build better products.
  3. Releasing work often and early is important for getting feedback. Instead of waiting for fixed time frames, developers should share updates when they're ready to adjust based on customer input.

The D.I.E. Triad - Applied to your Career (and Life)

Resilient Cyber • 279 implied HN points • 17 Jan 24
💼 Business Career development Professional networking Agile Methodology Digital Transformation
  1. Building a strong network is important for career resilience. It's not just about who you know, but who knows you and what you bring to the table.
  2. Some core values and work ethics should remain unchanged throughout your career. These qualities, like determination and discipline, help you stay successful as roles and technologies change.
  3. You should treat your personal and professional growth like a product that needs constant improvement. Embrace change and ask for feedback to keep evolving.

Proposed Addendum to the Manifesto for Agile Software Development

Rethinking Software • 199 implied HN points • 29 Aug 24
🕹 Technology Software Development Agile Methodology Team Collaboration Organizational Structure
  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.

Weekly Notes

Rethinking Software • 149 implied HN points • 23 Sep 24
🕹 Technology Software Development Agile Methodology Product Management Team Dynamics Data Analysis
  1. Story points are basically just hidden time estimates for tasks in software development. Understanding this can help with better planning and predicting when a project will be finished.
  2. Product management should be like a party host, making sure developers and customers communicate and enjoy their time together. This creates a better experience for everyone involved.
  3. There are ways for companies to run without traditional management, like the tomato processor Morning Star. This might be a model to explore for improving the software industry's workflow.

Weekly Notes

Rethinking Software • 99 implied HN points • 21 Oct 24
🕹 Technology Software Development Agile Methodology Coding Practices Team Dynamics
  1. Managing programmers can be unpredictable. It's important to accept that things may not always go as planned.
  2. Euphemisms in corporate language can hide unpleasant truths. Words like 'alignment' often mean forcing compliance rather than true cooperation.
  3. Scrum practices may not be effective for all teams. Some core principles can actually create stress and hinder productivity instead of helping it.

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.

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.

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.

TWH#50: Simple Explanations For Complex Phenomena

The Hagakure • 119 implied HN points • 16 Mar 23
💼 Business Product Management Software Engineering Agile Methodology Organizational Behavior
  1. Our brains seek simple explanations for complex phenomena due to our evolutionary history.
  2. Predictability and control in knowledge work are often illusory, leading to eroded trust and inefficiencies.
  3. Embracing uncertainty and complexity in work requires shifting mindset towards experimentation and adaptation.

Scrum's "Product Owner" Problem

Rethinking Software • 14 HN points • 03 Oct 24
🕹 Technology Software Development Agile Methodology Product Management Engineering Practices Team Dynamics
  1. Product Owners should provide information, not direct decisions. Engineers need real-time data to make informed choices, rather than just waiting for orders.
  2. Engineering teams should ask deeper questions to understand their customers and competitors better. This helps them create better solutions instead of just following a checklist.
  3. The relationship between Product Owners and Engineers should resemble a restaurant. Product Owners gather customer insights while Engineers create the dishes, allowing for better quality and innovation.

Episode 28: Burkhard on Qt Embedded Systems

burkhardstubert • 39 implied HN points • 04 Apr 22
🕹 Technology Embedded Systems Software Development Programming Cloud Computing Agile Methodology
  1. Burkhard is switching from a newsletter format to a blog for sharing his thoughts on Qt Embedded Systems. He believes this will help him attract more readers and focus better on his writing.
  2. There are different levels of architecture diagrams for Qt embedded systems, such as context and container levels. These diagrams help in understanding system interactions and can guide the organization of development teams.
  3. Spotify uses a unique structure for its teams, like squads and tribes, to encourage communication and collaboration. This approach helps address dependencies between teams and enhances productivity.

The Scrum Survival Guide: How to Make Scrum Work (Maybe)

Rethinking Software • 2 HN points • 21 Sep 24
💼 Business Project management Agile Methodology Team Dynamics Organizational Behavior Software Development
  1. Using longer sprints can give teams more freedom and reduce stress over estimating work. It allows developers to manage tasks more effectively without getting stuck on details.
  2. It's important for developers to have control over their meetings and tools. Letting developers run their own stand-ups and choose simple tools can improve efficiency and morale.
  3. Teams should focus on collaboration and flexibility. Allowing for specialization in tasks and removing unnecessary management roles can lead to better job satisfaction and productivity.

The Role of a System Architect

The Incrementalist • 1 HN point • 08 Aug 23
🕹 Technology Architecture Agile Methodology Career progression
  1. Having a System Architect can lead to improved alignment and coordination across teams, enhanced technical expertise, improved quality and performance, and reduced technical debt.
  2. The role of a System Architect can harmonize with the Agile methodology by providing guidance and direction to teams on technical aspects while being a facilitator and coach.
  3. Guiding principles for a System Architect include valuing people, effective communication, simplicity in design, embracing change, customer-centric solutions, delivering quality, and agile documentation and modeling.

On communicating why software is late

Thoughts from the trenches in FAANG + Indie • 0 implied HN points • 17 Jun 23
🕹 Technology Software Development Project management Agile Methodology Stakeholder engagement
  1. Software projects often experience delays, especially when creating new software. It's important for both engineers and stakeholders to work together and understand how to communicate about these delays effectively.
  2. Clear communication about the project's delay is crucial. Everyone should know the new expected delivery date, what caused the delay, and what is being done to fix it.
  3. It's helpful to regularly share updates about the project's progress. Using a simple color system can show how likely the project is to meet deadlines, helping everyone stay informed and manage expectations.

Breaking Batches: How Batching Undermines Agile Software Development

Wisdom over Waves • 0 implied HN points • 25 Jan 24
🕹 Technology Software Development Agile Methodology Quality control Continuous Integration
  1. Quality is proportional to the quantity of feedback - more feedback means better quality.
  2. Batching is inversely proportional to quality - more batching leads to lower quality.
  3. Decreasing batching can be done through an Agile mindset, automated Continuous Integration/Deployment, feature toggling, early testing, breaking down large features, using MVP approach, and improving team communication.

How to understand deadlines (as a developer)

Bad Software Advice • 0 implied HN points • 28 Jan 25
🕹 Technology Software Development Project management Product Design Agile Methodology Technical Debt
  1. Deadlines can make developers feel rushed and stressed. It's common to make quick fixes that won't last, leading to more work later.
  2. Developers often don't see the bigger picture of a project. They might not understand why a 'bad' version of a product is needed to learn what works best.
  3. Not every project needs to be perfect from the start. Sometimes you need a rough version to figure things out before building something better.

You’re Iterating to Nowhere

realkinetic • 0 implied HN points • 21 Feb 18
💼 Business Strategic Planning Process Improvement Goal setting Agile Methodology
  1. Teams working towards a shared vision are more efficient and deliver more value. Clear vision empowers team members to make better decisions independently.
  2. Having a shared vision prevents teams from iterating aimlessly. It provides direction and purpose to the team's efforts.
  3. Strategic planning with high-level vision and concrete goals is essential for project success. Combining agile for day-to-day tasks with strategic planning ensures consistent delivery of value.