r/agile • • Dec 26 '24

How Agile Purists Are Failing Modern Businesses

0 Upvotes

The problem with the so-called purist view of Agile can be summed up in the typical conversations you have with its advocates:

•	Setting hard deadlines? Bad thing.
•	Using sprints? Bad thing, reinforces a deadline-driven approach, which is “anti-Agile.”
•	Reporting? Bad thing, not needed—just trust the team.

Their whole mindset toward delivery boils down to: “It will be done when it is done.” Or simply: “Just trust me, bro.”

What does that show?

•	A lack of commercial awareness.
•	A lack of respect for organizational goals.
•	A lack of respect for the organization’s finances, assuming teams have unlimited time to deliver outcomes on their terms.

This approach is completely detached from the realities of business.

To remain competitive, organizations need visibility over the direction they are heading, and that’s impossible without any real plan or structure in place.

Furthermore, these purists are quick to criticize companies not adopting Agile in its purest form but then conveniently ignore the fact that the companies generating millions annually with a structured approach must be doing something right.

Take Elon Musk, for example—known for being extremely deadline-driven, setting aggressive timelines. That would not be compatible with the “it will be done when it is done” mentality or a lack of planning. So, are they really the ones doing it wrong?


r/agile • • Feb 07 '24

What Are Spikes and How to Estimate Them?

0 Upvotes

Spikes are special stories or work items and they are handled slightly differently.

When we work on a project, there are different kinds of work items. Some are about modifying existing functionalities and some are about creating new ones. There are also work items which help make the project better, such as enhancing its performance, faster speed, better look and feel, etc. While creating new functionalities is about understanding the requirements, making the project better or smarter might need some research to be done to create the right requirements. This latter work is what spikes are all about.

Let us understand spikes by visiting a few examples.

Story 1: As a baker, I like to bake pumpkin bread so that I can reward my kids for the chores they do.

Story 2: As a baker, I would like to bake pumpkin bread with a different flour than I am used to, so that I can surprise my kids with a delightful new flavor.

I usually bake using all-purpose flour (Story 1). But what happens if I want to use a different flour (Story 2)? For example, for Story 2, I could use semolina flour, or whole wheat flour, or cake flour, etc. Now, in order for me to understand relatively how complex it is to bake with a new primary ingredient (type of flour in this case), I may have to do some research. So looking at the examples above, the effort needed in Story 2 may not be estimable unless I do some research.

This calls for a spike*. An example is given below.

Spike: Research what is needed in terms of equipment, precautions, handling the new ingredient in certain specific ways, preparation, instructions etc., to bake effectively using flours that is different from the usual whole purpose flour.

Bringing this back to software development, similar research backlog items are called Spikes. Spikes are therefore created for the team to gain more information before an actual story related to a functionality can be estimated. They are meant to bring clarification to our functionality. Spikes are timeboxed, meaning that the team in agreement with the Product Owner or with their support, decides to invest, say N hours of research and bring out information that can help estimate the work in implementing the functionality.

This is similar to the metaphor of a rock climber hammering a spike into the rock**. Although the climber may not be climbing at that moment, the spikes they are working on would still enable them to move forward with their work.

After these N hours or so of work that is done in a sprint, the team pauses and shares the research with the Product Owner. At that time, the Product Owner decides if they have enough information to move forward with the project or they may request for additional spike items that are timeboxed to another chunk of hours. This is how spikes are timeboxed.

But the bigger question is, how do we include a timeboxed spike as part of our velocity (the amount of work delivered in a sprint expressed in terms of total number of story points)?

Here’s one way it can be done. As an agile team continues to work for a few iterations, they realize their story points have certain (hour/time) ranges. For example, a 1-point story could range from 2 to 8 hours. The best case 1-point story may take around 2 hours, and the worst-case story might take around 8 hours (These are hypothetical numbers and can be different for different teams). In the same way, the 2-point stories could range between 4 to 13 hours (again, hypothetically speaking). Once this relationship is established between story points and hours for a team, it is easier to convert timeboxed spikes to story points. Say, a team wants to now timebox a spike of N=20 hours, they can map into a relevant story point (for example it could be their 3-point story range). This is a good, organic way to provide story point estimates for your spikes.

This exercise of story point vs. hours is usually facilitated by the Scrum Master working with the team after the team has completed a few sprints. This relationship between story points and hours also helps the team improve its story point estimation accuracy.

But what about a team that still hasn’t figured out their story-point-to-hours relationship? Either the team isn’t estimating consistently, or isn’t estimating as a team, or they don’t understand the story point estimation. Or it could even be that they have just started working together as a new team. For such teams, it is recommended that they start with some kind of a range. But they should be open to taking feedback from their actual work items as they move on from sprint to sprint. It is not recommended to fix a number of story points to a fixed number of hours as is prescribed by some scaling frameworks.

What are your thoughts? How do you normally estimate your spike backlog items?


r/agile • • Apr 01 '26

AI agents forced us to completely rethink our agile PDLC

0 Upvotes

Is it just us or did AI agents break your agile process too? We reworked our PDLC from scratch and now it honestly looks like waterfall. But we iterate more in a week than we used to in a sprint. Genuinely want to hear if you had the same experience in the last months???

We are a team of 8. 2 PMs, 5 engineers, 1 designer. 6 months ago we went all in on Claude Code.

First thing that broke: sprints. Features getting implemented in hours. Weekly sprints stopped making sense. So we dropped them.

Second thing that changed: how we plan. AI agents take your plan literally. A good engineer reads between the lines of a vague ticket. An agent doesn't. It builds exactly what you wrote, nothing more. That forced us to get way more specific in planning than we ever were with Jira.

So we killed Jira too.

What we do now: plan one feature at a time. PM, engineer, designer, AI work together in real-time. AI has codebase context, flags contradictions, suggests simpler approaches. PM describes the feature in natural language, debates the technical tradeoff, makes the call.

Plan locked. Agents implement. PM reviews the outcome. Ship or adjust. Same day.

No sprint planning. No estimation. No grooming. No standups where people read ticket statuses.

The agile values are more alive than ever. We respond to change in hours. We ship working software daily. We collaborate more, not less. We just killed every ceremony because they were built for a world where implementation took weeks.

What I didn't expect: everyone's happier. Engineers love it because when an agent fails the implementation, they pick up a well-defined ticket with full context instead of a vague mess. PMs love it because they finally get exactly what they asked for. No more "that's not what I meant."


r/agile • • Jun 29 '24

It's time for the Software developers to take back the Industry from the Parasites

0 Upvotes

For the last 10-15 years, we have seen how the Agile manifesto has been bastardised by the likes of McKinseys, Scrum, SAFe etc. and the entire consulting industry that sprung around it, created whole new set of careers that are basically parasites eating off the real software developers who do the actual core work in software development.

An entire generation of young developers have grown up in this toxic BS culture of ceremonies, methodologies and meetings that no one wants to attend and bureaucratic red tape that have been imposed on them. They don't even know any other ways of working.

At least for sake of our industry and for the future generations, it's h time that we take the Industry back from the Parasites - the Agile coaches, the SMs, the useless POs who don't talk to the customers but make up sht as they go along just to show fake progress and finally the clueless top management who think they can copy and paste methods suggested by the consulting companies and it will work after they leave.

Rebel against BS at all levels, ask questions to the agile coaches what's the proof that the shtty processes they want us to follow will work, why the real top companies in tech don't follow whatever is sold to other companies, why we should listen to them when they don't have any experience in even low level programming etc. Don't blindly give estimates, ask who needs it and for what, what happens when the estimates can't be met etc. Use the Engineering and Tech managers to push back and resist. We shouldn't let the Parasites dictate our area of expertise anymore. No other Industry faces this - why should Tech be the only scapegoat for the fake agile consultancies to make money ?


r/agile • • May 04 '25

Agile isn’t bad. It’s just not enough.

2 Upvotes

We’re trying to use a system built around productivity to manage something that’s actually about timing and coherence.

We’re acting like software is a factory line.

But real work — the meaningful stuff — doesn’t follow a Gantt chart.

It breathes. It spirals.

So here’s what I’ve been experimenting with:

It’s not a framework. It’s a rhythm.

No capital letters. No book coming. Just a pattern I live by now:

Seed → Spiral → Collapse → Echo

Let me unpack it like a human, not a consultant:

Seed = Wait.

  • We stop. We listen. Not to “stakeholders” — to what’s emerging.

  • Sometimes the best thing you can do is not start yet.

  • We tune to the right problem, not just the loudest one.

Spiral = Explore.

  • Not commit-and-sprint. We orbit.

  • Design, prototype, test, trash, try again.

  • The work deepens. We spiral inward. Clarity rises.

  • It’s not slower. It’s smarter.

Collapse = Ship.

  • This is the click. When the timing, the insight, and the build all snap into place.

  • It feels right. The release doesn’t exhaust the team — it energizes them.

  • You know when it’s time. No burndown chart needed.

Echo = Listen.

  • After the release, we don’t just retro. We absorb.

  • What changed? What landed? What rippled?

  • Then we rest.

  • And the next Seed shows up.

This isn’t me being anti-Agile.

This is me being tired of pretending this is working.

I want to build things that matter, at the right time, with people who aren’t burned out zombies pretending they’re “on track.”

If any of this resonates — or if you’ve felt that low-grade Agile despair — I’d love to hear how you’re navigating it.

Because I don’t think we need better methods.

I think we need better rhythms.

(Yeah, I know that’s weird. But breath is where the real backlog lives.)


r/agile • • Sep 10 '25

Agile is a waste of effort

0 Upvotes

I’ve been a Python developer for a few years, and I just recently discovered Agile. Bottom line: I hate Agile and it should never have been made in the first place.

Agile is nothing more than a concept that gathers common sense practices, packages them into buzzwords that have no relation to those practices, and then shoehorns unnecessary actions and requirements that actually prevent any real work from getting done.

For example, one of the related Agile concepts is Lean. In Lean, one of the main goals is to eliminate waste in the development process. Well no shit! Show me a business that intentionally adds waste to projects, or one that desires to make development as slow as possible.

In Python programs I have made, testing the program is done constantly. Yet Agile gurus like to characterize other development processes, like the “waterfall” method, as being so rigid that testing the program is not allowed until the project is completed. Furthermore, Agile demands that testing be done in pre-planned chunks called Sprints, which are meticulously managed. This only adds waste to the entire project.

But that brings me to another point: terms used in Agile make no sense at all. A user story is a Yelp review or something similar, an experience a user had while using the software. But in Agile, a “user story” is a software requirement. How does that make any sense? Who is the buffoon that decided the term “user story” is a product requirement?

There are more nonsense terms. Story point sounds like a plot point in a novel or a movie. But in Agile, “story point” is defined as a vague way of measuring one “user story” against another. The word epic is an adjective, but Agile turns “Epic” into a noun and defines it as a collection of “user stories” that have been met. A sprint is a short, fast run, but in Agile it is a pre-planned and pre-approved block of testing. A spike is a sharp stake in the ground, or a steep peak on an xy graph. But in Agile, a “Spike” is a block of time used for research. The word scrum is a term for mass confusion and chaos, but in Agile, “Scrum” is a method for implementing Agile. Of course, given the asinine framework of Agile, I would not be surprised if using “Scrum” did cause confusion. How do these terms make any intuitive sense?

Agile claims to be a flexible framework, but “Sprints” and “Spikes” must be pre-planned, “user stories” must be presented in a rigid format, and “story points” are required but are so loosely defined, they could mean anything.

Agile takes common sense approaches to project development and repackages them as something that no one has ever thought of before. For example: “Arrange teams and tools needed to optimize production”. Is there a successful business that does not do this? “User feedback is critical”. When has user feedback ever NOT been critical? “Set clean communication guidelines for your teams”. Oh wow! You mean that teams that don’t communicate won’t be successful? Who would have thought?

Agile is nothing more than a useless management tool. Superiors who know nothing about code can become Agile managers and then get to call themselves software engineers, without contributing any real effort to the project. A company that implements Agile will suddenly need to hire more people to oversee the Agile process and pretend to lead a team in software development. And guess who will get the credit for making the software? Not the coders, but the manger who doesn’t have to know any code at all. I sincerely hope that I will never have to work in an Agile environment.


r/agile • • Dec 29 '22

Are stand ups/dailys just a fancy idea to control employees?

0 Upvotes

I’m sure they are useful to some extent but I feel that those meetings are often just an excuse to check on employees and make sure no one’s slacking?


r/agile • • Jul 28 '26

daily standup is killing me

0 Upvotes

We spend thirty minutes taling about what we did yesterday and zero minutes actually coding. This process is supposed to help but it just adds bloat. Anyone else feel like like their scrum master is just obsessed with metrics?


r/agile • • Mar 06 '26

Learning React changed how I see engineers

1 Upvotes

I’ve been learning React in my spare time and recently got to the point where I can build small apps.

Before I started learning, when working with engineers I’d sometimes hear comments implying I should already understand certain technical concepts. If I asked questions, the response could occasionally feel dismissive.

Since actually building things myself, I’ve realised two things:

1.	Engineering is more complex than it often looks from the outside.

2.	Some engineers assume others should already know things that are obvious to them. Not taking into account that other people are not living and breathing code in the same way they are.

This can make them difficult to work with.

Curious to hear from both engineers and product/delivery folks:

•	Have you seen this gap before?

•	Does learning to code change the dynamic?

r/agile • • Feb 14 '26

My backlog is basically just a history book now. Does AI kill the 2-week sprint?

38 Upvotes

Serious question. My team is heavy on AI agents and the velocity is actually scary.

I feel like a historian documenting what already happened rather than a PM planning what will happen. By the time I write a proper user story or set up a sprint board, the feature is built, tested, and sometimes even deployed.

Standard Scrum rituals feel like trying to traffic control a race car with a stop sign. It’s just getting in the way.

  • For those with hyper-productive, AI-native teams: What is the new meta?

  • Are we shifting to continuous flow/Kanban? Dropping tickets entirely?

  • How do you manage a team that codes faster than you can think?


r/agile • • Oct 21 '24

Stand Ups are Genuinely Awful

4 Upvotes

For context, my workplace adopted Agile and Scrum 7 years ago. And I quickly felt its issues. But I have a particular loathing for the Stand Up. This fifteen minute meeting every day is a massive killer of productivity. And many people don't even realise it.

Let's say, you start work a 0900 and your stand up is at 0930. That first half-hour of your day? You can't do anything with that. That's just gone. So your 15 minute meeting is actually a 45 minute meeting in disguise. Then after your meeting, it generally takes 30 to 60 minutes for a developer to get back into the workflow state. So by the time you're actually doing anything productive, it's 1045. You've lost almost a quarter of your day, and lunch is not far away now.

Basically, no-one is productive to any real degree before lunchtime.

Not to mention, you've got meetings for things like sprint planning and retrospectives, among other things that seem to exist purely for someone to listen to their own voice. These are a huge waste of time. Time that can be spent doing development work. What I'd rather have, is a manager that goes to those meetings for the whole team, then provides development notes in an email.

I don't believe that developers need to go to all these meetings to get their work done. In fact, I find that they're detrimental. All that I've seen these do in my workplace is waste our time and lower our productivity. But at least the people above us get to micromanage us and complain about the lack of productivity and morale.


r/agile • • Sep 05 '15

My lady friend is committed to the process (NSFW) NSFW

Thumbnail
imgur.com
0 Upvotes

r/agile • • Oct 08 '25

Do you do "Acceptance Criteria" in Scrum? Shouldn't they be implicit?

2 Upvotes

One of the teams I manage cane up with an interesting issue that some of the team members seem to struggle with:

They lack acceptance criteria in User Stories before taking them into the sprint, or even: before sizing.

Personally, I have a problem with that. IMHO, there should be no such thing as "acceptance criteria" in the ticket, before starting the work on it. For a few reasons:

  1. It's per-ticket-waterfall. You want to write down the exact details of how the final product should work.

  2. It forces you to do complex work as a part of the refinement process. A work that should be done as a part of the sprint.

  3. "Working software over comprehensive documentation" - instead of doing the software, you do comprehensive documentation spread across the tickets

  4. Quality assurance is part of the work, and the people specializing in QA should do their work in an agile way, rather than be mindless drones ticking off the acceptance criteria. Similarly, developers should do the work in an agile way, rather than being replacements for an LLM, that needs a very specific prompt to do the work. Having a written acceptance criteria at all is IMHO doing more harm than good, when it comes to setting the right mindset within the team.

If it helps, for added context: None of the customers cares about any documentation or any of the QA processes. We have a fairly high customer tolerance to faults in our product. We do not do TDD, but we do have a fairly good amount in automated tests (>80% coverage) + we have a dedicated QA. Our product owner would rather not have the acceptance criteria at all, but he doesn't mind it team writes them down. And finally: Our user stories are written in value format - As <who>, I want <goal> to <value/benefit/the why>.

So... do you do acceptance criteria in your tickets (be it User Stories or otherwise) in Scrum?

What are your thoughts about implicit acceptance criteria? (By implicit I mean: it's not written down, BUT the team's knowledge, combined with test automation, should cover all the goals of a written acceptance criteria)


r/agile • • Feb 20 '20

Anyone interested in Scrum Master Certification Course Coupon UDEMY - FREE

0 Upvotes

Hi I was just wondering if anyone would be interested in Scrum Master Certification Course Coupon UDEMY - FREE.

Please drop me a private message and I will send you the code. I have got few left with me.


r/agile • • Jun 23 '26

Is the Scrum Master role still a good profession to go into?

0 Upvotes

What are the community thoughts?


r/agile • • Nov 01 '15

Why Agile isn’t the answer.

Thumbnail
weshigbee.com
0 Upvotes

r/agile • • Jun 13 '25

Tedious agile tasks / scrum meetings that could be automated by AI?

0 Upvotes

Without a doubt there are some elements of strong agile practice that feel deeply human--creating a safe space that encourages participation, tight communication and feedback loops, etc. but as agentic AI takes on a more prominent role for tech companies that are using scrum, are there any tasks (or entire meetings) that you anticipate will be the first to be automated or performed by AI?


r/agile • • Nov 16 '21

I still don't understand minimum product

0 Upvotes

No matter how often it's explained to me it doesn't make sense. I don't understand why you would release 'minimum' anything, or any product at all with less than full functionality. If I am asked to build a house why would I not put on a roof? If I'm building an app that's supposed to do 7 things and it only does 3, I haven't delivered what I promised.

I keep using software developed using Agile and I keep running into issues, and am told "oh you can't do that yet, that functionality is being released with the new update." This just doesn't make any sense to me. If it's meant to do a thing, and doesn't do that thing, in what way is it worth releasing? The whole thing just seems to be based around 'completing' projects quickly, instead of well.

EDIT/UPDATE: General theme of the comments and replies seems to be that it's largely because clients/customers/managers don't know what they want and while I agree, I don't really see why that's your problem. If I decide I want to eat a sandwich and afterwards I realise I really wanted a pizza, it would be bizarre behaviour to get mad at whoever made the sandwich.

EDIT/UPDATE 2: I also understand now that as an end user, I'm not the one you want to please with the design process. I appreciate the desire for your company to do well and get new clients, but I have some bad news for you about your value to the company. But that's by the by. I do understand the value for a tech CEO, just not for me as a user or really a developer.

EDIT/UPDATE 3: Finally we got there. It's about reducing your workload. Got it. That took ages.

ADDENDUM: Please give us the final product. You can show our bosses as many iterations as you like. We want the complete version.


r/agile • • Nov 19 '24

In the age of Gen AI, isn't the current method of managing a scrum archaic ?

0 Upvotes

I have been using agile and scrum methodologies for the past several years while working for companies like Amazon, Microsoft, Palo Alto Networks, NetApp etc. and one thing that I used to get bored off was the different sessions like Backlog Grooming, Planning Poker, Scrum, Retrospective etc. I do see a point in those processes and sessions, but I feel that in today's age, these processes can be fused and made more productive. I feel almost all the tools that we use are simply record keeping tools and are not smart enough to eliminate the drudgery that goes into maintaining a healthy scrum for a 1 pizza team or even higher. What does the community think ?


r/agile • • May 10 '25

"AI projects" management is not linear, it deserves a new discipline altogether!

3 Upvotes

I’ve managed both traditional software development and AI/ML projects in my career across FMCG, Banking , Telecom, and Health care. while both have their own life cycle and chaos, AI projects are different entirely and felt managing AI projects are 10x harder to scope, govern, and align, even with senior teams.

Traditional software development is straight forward - You hit acceptance criteria and move on. But
AI? You're constantly retraining, re-validating, and dealing with model drift.

Over time It’s not "did the feature work?" It’s "is 84% precision good enough in production?" And everyone from product to legal has a different opinion. The project plan for AI projects is never linear.

Honestly, I think AI project management deserves its own discipline !!


r/agile • • Dec 11 '25

I watched requirements meetings fail for years. Here's the masterclass in everything you should NOT do (Part 1: Preparation)

3 Upvotes

You know that sinking feeling when your requirements session turns into chaos? Three people are missing. Two are scrolling phones. One executive is explaining exactly what button he wants before anyone's agreed on what the system should actually do.

I've been documenting requirements gathering disasters, and honestly? We keep making the same mistakes.

Here are the preparation anti-patterns that doom sessions before they start:

The vague invite trap Sending "Requirements Meeting" with zero description. No context, no preparation time, just confusion. Then burning 20 minutes explaining what everyone could've read days earlier.

Inviting the wrong people (or everyone)

  • Inviting by job title instead of actual knowledge

  • Missing the end users who actually live in the system daily

  • Or inviting 20 people "just to be safe" and watching chaos unfold

Winging it without questions Walking in thinking "I'll go with the flow" sounds flexible. In reality? You ask "So... what do you want?" and watch people struggle with such a broad question. No guide means you miss critical areas or chase tangents that don't matter.

The fix isn't complicated:

  • Send clear agendas several days ahead

  • Invite people with actual knowledge and stakes in the outcome

  • Prepare flexible question guides (not rigid scripts)

This is Part 1 of my 3-part series on requirements gathering failures. Parts 2 and 3 will cover how NOT to conduct and close these sessions.

Read the full breakdown on Medium.

What requirements meeting disasters have you witnessed? What would you add to this anti-guide?


r/agile • • 17d ago

Is there a future for Story Mapping?

0 Upvotes

Hi all,

I'm the creator of Cartographer and I'm looking for some input from the community.

Story mapping is something I really like, but it feels like it's losing it's utility. I had thought that perhaps it would become more useful because when engineering teams are capable of building more quickly, having a view of the big picture becomes necessary to keep everyone on the same page.

But to be honest I'm not seeing that. More and more users of my tool are solo users, who are not using it to communicate and align: they're using it to build, feed their agents, more like a fancy kanban board. Which I suppose is fine, but isn't quite what I made it for :)

Actual story mapping as a way to align and communicate feels like it's in decline. Is this something you're also seeing? I'm trying to find a way to renew the tool, or adapt it to how people are working these days, so I can keep it relevant... but I'm not really sure what threads to pull at.

Thanks in advance for any ideas/input on the matter!


r/agile • • Sep 18 '21

5 Types of Agile Methodologies You Can Use in Your Projects

0 Upvotes

A few years ago, Scrum used to be the only Agile methodology. But, times have changed. Right now, there are more than fifty known Agile methods.

So, what is Agile? Agile is a form of project management style that is iterative and incremental in approach. Its leading use is in software development, but not limited to it. It differs from traditional project management as it is very responsive to change.

In this article, you will learn about Agile methods, how they work, and how to use them in your projects.

  1. Scrum

Scrum is one of the most popular subsets of Agile methodologies. This method was created by Ken Schwaber and Jeff Sutherland, who define Scrum as a framework for developing and sustaining complex products.

In Scrum, you divide the work into units called sprints. A sprint is a set time that a Scrum team works to complete a set amount of work. The Scrum Master, who leads the Scrum team, creates the sprints and organizes the work.

Through the daily Scrum (that usually happens in the morning), every team member reviews their performance for the past 24 hours. Then, they are briefed with the sprint goals for the next 24 hours, and everyone gets to work. If a team member needs help, the Scrum Master helps them resolve it.

The Scrum method is scalable and flexible. It is best suited for projects that change rapidly and need the flexibility to change as the project evolves.

2. Kanban

The origin of Kanban is in car manufacturing. It is a method that optimizes every stage of the production process and ensures production is just in time. Today, Kanban has evolved beyond manufacturing and is now widely used in project management.

So, what is Kanban? Kanban is a workflow project management approach that helps you visualize your work and ensure a smooth flow of your work. When using the Kanban method, you use a Kanban board that visualizes your work into three columns. Those columns are To Do, In Progress, and Complete.

Each column has a Work In Progress (WIP) limit that limits the number of items under a column. So, if a column has a limit of four, there cannot be more than four cards on it. If a column is packed, your team has to work on the items on the columns before moving forward or adding more cards.

Kanban is ideal for knowledge work that is often not tangible. Having the visualization helps you see what you're working on.

3. Adaptive Software Development (ASD)

The Adaptive Software Development Agile methodology was developed by Sam Bayer and Jim Highsmith in the early 90s. It was created as a refinement of Rapid Application Development (RAD) that was popular with hackers. ASD's strong point is that it handles the uncertainty in software development and fosters collaboration.

ASD, just like other agile methods, works in iterations. However, it differs from the rest as the iterations are component-based and not task-based. These components are a group of features that are delivered together. They are grouped into three: primary components, technology components, and support components. It allows for on-time delivery of projects, and in some cases, even earlier.

The drawback of ASD is that it demands intense user involvement. And, in some cases, it may be difficult to facilitate. Another draw is that ASD is change tolerant and adopts shorter time-frames. That can lead to scope creep during projects.

4. Dynamic Software Development Method (DSDM)

Dynamic Software Development Method (DSDM) is another Agile methodology developed from Rapid Application Development (RAD). It brings structure to the free-form of RAD. Its philosophy is that any project must have clear goals and should focus on the early delivery of its goals.

This philosophy is backed by its eight principles, which are: focus on the business need, delivering on time, collaborate, don't compromise on quality, build incrementally, develop iteratively, communicate clearly and continuously, and have control.

DSDM uses the MoSCoW prioritization method of productivity that groups tasks into four priorities. Those are must-have, should-have, could-have, and won’t-have. This method helps if you have budget constraints and gets you to prioritize the must-haves of the project. Also, if there is a constraint on expertise, it prioritizes work based on the skillsets already on your team.

Another feature of DSDM is timeboxing. DSDM sticks to strict deadlines, and it does that by breaking down the project into smaller units that have a deadline and tight budget. Other than that, it is also strict on the order of events in a project. It has them as Pre-Project phase, Project Life-Cycle phase, and Post-Project phase.

5. Feature-Driven Development (FDD)

Feature-driven development is a client-centric and pragmatic approach in software development. Its first use was in 1997 to develop software for a Singaporean bank. Since then, it has grown as an approach. It is now mainly used in long-term complex projects that need a simple but comprehensive approach.

FDD's structure is straightforward, and teams with complex projects can scale it to meet their needs. Unlike other Agile methods that are iterative and incremental, FDD follows five steps. These are:

  1. Developing the Overall Model

It covers the scope of the project.

2. Build a Features List

Identify all the features that are to be built. For this, no feature should take more than two weeks to build. If a feature takes longer, you break it down into smaller features.

3. Plan by Feature

Arrange the order in which the features are to be developed and implemented.

4. Design by Feature

Design and build a feature in a two-week iteration. When complete, there is a review of it by the team before developing the next feature.

5. Build by Feature

The completed feature in step-4 is added to the main build.

These steps are borrowed from engineering best practices and create consistency in a project. These also help reduce confusion and rework as everything is clear from the get-go.

Be Agile

Traditional project management methods like linear have been around for a while. They are steady and predictable. However, they have their limitations. One of the main ones is that they're slow in responding to the changes in the market.

This is where Agile comes in. Agile project management may be the newcomer in project management compared to the rest, but it is highly adaptable to the changes in the market. It has shortened product development timelines, increased productivity, and empowered teams to develop great products.

What Is the Agile Programming Methodology?

Whether you're applying for programming jobs or you want a more efficient way of working, you'll need to know about Agile.

About The Author

Hilda Munjuri (23 Articles Published) Hilda is a freelance tech writer, and enjoys keeping up with new tech and innovations. She also likes to find new hacks to save time and make work easier. In her free time, you will find her tending to her vegetable garden.


r/agile • • Feb 16 '24

There's No Such Thing as Failure!

0 Upvotes

Don't let a closed door define you. It's not failure; it's feedback!

In life, setbacks aren't the end; they're opportunities for growth.

When you face a closed door or find yourself at a crossroads, it's not a signal to give up. Instead, view it as valuable feedback.

I took up rollerblading at 35 taught me this lesson profoundly. The fear of falling was real, but every tumble was a piece of feedback. I didn't shy away; I set up guardrails—precautions to keep me safe as I practiced. The feedback was transformative. In a few months, I wasn't just rolling; I was able to jump curbs, hurdles, and was able to embark on long hikes with newfound confidence.

This mindset is easily applied to any journey. Whether you're stepping into the role of a Scrum Master, an Agile Coach, or a leader, perfection won’t come overnight.

Fully immerse in the journey, welcome feedback, and evolve. Every stumble is a stepping stone to growth. My most significant strides in the Agile field weren't marked by failures but by lessons learned through feedback.

Remember Steve Jobs. He was once ousted from Apple but didn't give up. He went on to create Pixar and NeXT and, eventually, returned to lead Apple to unprecedented heights.

Setbacks aren't roadblocks but stepping stones to success.