The hottest Process Improvement Substack posts right now

And their main takeaways
Category
Top Business 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.

Issue #15 – The Data Quality Conundrum (Part 1 – Root Causes)

The Data Ecosystem • 399 implied HN points • 21 Jul 24
💼 Business Data Quality Management Analytics Governance Process Improvement
  1. Poor data quality is a big problem for organizations, but it's often misunderstood. It's not just about fixing bad data; you need to figure out what's causing the issues.
  2. Data quality has many aspects, like accuracy and completeness. Good data helps businesses make better decisions, while bad data can cost a lot of money.
  3. To solve data quality issues, you need a complete approach that looks at different root causes. Simply fixing one part won't fix everything, and different sources might create new problems.

Issue #12 – The Three Biggest Data Problems Companies Face

The Data Ecosystem • 239 implied HN points • 30 Jun 24
💼 Business Data Management Organizational Structure Process Improvement Data Quality Technology Integration
  1. Companies often struggle with a data operating model that doesn't connect well with their other teams. This leads to isolation among data specialists, making it hard to work effectively.
  2. Data models, which are important for understanding and using data correctly, are often overlooked. When organizations don’t reference these models, they can drift further away from their goals.
  3. Many data quality issues come from deeper problems within the organization, like poor data governance and inconsistent processes. Fixing just the visible data quality issues won't solve the bigger problems.

TBM 326: Adhocracies and Bureaucracies

The Beautiful Mess • 489 implied HN points • 06 Dec 24
💼 Business Organizational Behavior Corporate culture Leadership Management Practices Process Improvement
  1. Rapid-growth tech companies often start as adhocracies where everyone works quickly and independently. But as they grow, they can develop unspoken rules that make things complicated.
  2. Larger companies tend to have strict bureaucracies with many rules that can slow everything down. When they try to change, they often need to untangle these rules and make things simpler.
  3. Leaders often try to eliminate bureaucracy, but this can lead to even more hidden rules. It’s important for teams to talk openly about processes to solve problems effectively.

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

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

Quality Engineering Basics: Incident Reports

QUALITY BOSS • 39 implied HN points • 05 Apr 24
🕹 Technology Quality Engineering Process Improvement Software Development Engineering Management
  1. Incident reports help us learn from mistakes without blaming anyone. By understanding what went wrong, we can improve processes and avoid future issues.
  2. Writing incident reports takes time but leads to fewer problems later. They keep everyone informed and help prioritize important improvements.
  3. To make incident reports effective, clear criteria and responsibility are needed. It's important to track action items so that lessons learned actually lead to real changes.

Quality Engineering Basics: Bug Retrospectives

QUALITY BOSS • 39 implied HN points • 05 Feb 24
🕹 Technology Software Testing Quality Engineering Team Collaboration Process Improvement
  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.

When is the "Right time" for Culture Change?

🔮 Crafting Tech Teams • 19 implied HN points • 02 Jul 23
💼 Business Productivity Technology Process Improvement Learning
  1. Delaying cultural change can hinder productivity by increasing irrational thought-patterns and the challenging tasks ahead.
  2. It's essential to address difficult tasks promptly, such as learning new technologies or improving recurring processes, to avoid accumulating a backlog of tasks.
  3. Take proactive steps to prevent delaying important changes and maintain a balance in addressing various tasks effectively.

Quality Assistance, Not Assurance

QUALITY BOSS • 0 implied HN points • 18 Oct 23
🕹 Technology Software Development Quality Engineering Team Collaboration Process Improvement
  1. Quality Assistance means Quality Engineers work closely with developers. They help ensure high-quality software by sharing best practices and tools, rather than just checking for mistakes later.
  2. This approach moves away from the old method where a separate QA team is responsible for quality. Instead, everyone in the organization shares the responsibility for maintaining quality throughout the entire development process.
  3. Finding and fixing bugs early saves time and money. Waiting until the end of a project to test can cost a lot more if errors are found later.

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.

Kanban Quickstart

Certo Modo • 0 implied HN points • 28 Jul 23
💼 Business Management Productivity Metrics Process Improvement Teamwork
  1. Kanban is an efficient process for organizing team work, especially for interrupt-driven teams like Site Reliability Engineering, Operations, IT, or Customer Support.
  2. Implementing Kanban provides visibility, measurability, and easy reprioritization of work, helping build credibility and trust with stakeholders.
  3. Key elements of effectively managing Kanban include tracking all work items, creating clear work state columns, limiting work-in-progress, and using metrics to drive continuous improvement.

Get Your Product Back On Track

Build To Scale • 0 implied HN points • 10 Oct 23
💼 Business Product Development Team Management Process Improvement Collaboration Startups
  1. Implementing a Product Council can improve visibility, predictability, and provide a standardized process to address common scaling challenges in companies.
  2. The Product Council involves key leaders from different business functions working together to review and approve development plans, ensuring alignment and awareness across departments.
  3. Regular Product Council meetings help drive alignment, reveal problems early, and increase collaboration between Product and Engineering teams, ultimately making the development process more predictable and effective.