Re-visit Basics: SDLC Models Part 2

Hello again, LinkedIn family! Following the great start and your good words from the first part of our SDLC models series (you can catch up here), I’m thrilled to continue our exploration and revisit the diverse world of software development methodologies. ??

In this continuation, we dive deeper into some of the more specialized SDLC models. Whether you're looking to refine your development process or simply curious about alternative methods, or as I revising something that studied a long time ago we will cover what is left from the list not covered last time and will try to make some sort of summary or a guide based on what how we can find what model seems to be the best fit for our need.

Fun fact: here is the album that inspired me during writing of this article, maybe slightly dark for the majority but I love Diary Dreams so if you haven't heard them before welcome to enjoy them.

Apple Music - https://music.apple.com/ca/album/under-a-timeless-spell/1734796462

Spotify https://open.spotify.com/album/3sUdVweE2RRaWblFQGI0ln

In this article, we will cover:

• Scrum at Scale: Transforming organizations into agile networks.
• Feature-Driven Development (FDD): Breaking down projects into specific, client-valued features.
• Dynamic Systems Development Method (DSDM): An Agile framework that integrates best practices from previous models.
• RAD (Rapid Application Development): Speed is key. Ideal for projects needing quick development.
• V-Model: Another extension of Waterfall that emphasizes quality through test planning.
• Spiral: Combines iterative development with risk management, perfect for large, complex projects.

Exploration Continues

Scrum at Scale is like taking the engine of a sports car, Scrum, and fitting it into an entire fleet of vehicles to power a massive, coordinated road trip across a continent. Originally designed for single teams, Scrum at Scale turbo-charges these principles to sync up dozens or even hundreds of teams under the same agile umbrella.

Here's how Scrum at Scale plays out:

• Modular Structure: Imagine each Scrum team as a car. In Scrum at Scale, these cars are grouped into convoys (modules), each focusing on different segments of the journey (areas of the product or service). While each convoy operates independently, they all follow the same map to reach a common destination—the organization’s overall goals.
• Two Tracks: The journey progresses on two parallel tracks: the ScrumMaster Cycle and the Product Owner Cycle. The ScrumMaster Cycle ensures all cars communicate and navigate effectively (coordination, deployment, process), while the Product Owner Cycle maps out the route for each team (product backlog, prioritization, release planning).
• Scaling Teams: Scrum teams, like individual cars, may align into a "team of teams" (known as a Scrum of Scrums, or SoS) to synchronize their efforts. Leadership roles such as the Chief Product Owner and Chief Scrum Master act like lead drivers, coordinating across multiple convoys to ensure everyone is heading in the right direction.
• Cross-Team Coordination: To manage inter-dependencies and ensure smooth integration among the convoys, structures like the Scrum of Scrums and the MetaScrum are in place. The Scrum of Scrums focuses on the operational side ("how" to drive efficiently), while the MetaScrum ensures all teams agree on the priorities ("what" roads to take).
• Focus on Performance: Regular pit stops (feedback loops and retrospectives) are essential for refueling and tuning up, ensuring that each car and convoy performs optimally and improves over time.
• Executive Action Team: At the helm, there’s an Executive Action Team, acting like the central command center, tasked with removing roadblocks that impede more than one team, aligning the entire fleet with strategic goals, and ensuring the Scrum at Scale protocol is efficiently powering the whole enterprise.

Feature Driven Development is like building a house room by room, focusing on getting each space just right before moving on to the next. In FDD, the software project is broken down into features, and small pieces of client-valued functionality that can be delivered in a short amount of time. It’s a bit like creating a shopping list of all the things you want in your dream house, then tackling each one bit by bit, checking them off as you go.

1. Develop an Overall Model: Start by sketching a basic blueprint of the entire project, like drafting a rough floor plan for a house.
2. Build a Feature List: Break the project into smaller, manageable features—distinct, client-valued functions similar to individual rooms or house amenities.
3. Plan by Feature: Plan the execution for each feature, akin to scheduling different contractors for parts of a construction.
4. Design by Feature: For each feature, create a detailed design, much like planning the specifics of each room with an interior designer.
5. Build by Feature: Construct each feature based on the design, bringing each part of the project to life like building rooms in a house.

Dynamic Systems Development Method is an agile project delivery framework, primarily used for software development. It's like a recipe that guides how teams can efficiently develop and deliver software projects.

Imagine you're planning a trip with friends, where you need flexibility to change destinations or activities as new ideas come up or issues arise. DSDM is similar; it emphasizes collaboration and flexibility, allowing teams to adapt as project requirements evolve.

DSDM shares some common ground with other agile methodologies like Scrum or Kanban, but there are also some unique features. For instance, similar to Scrum, DSDM has iterative and incremental development, which means the project is broken down into smaller, manageable sections that are completed in short cycles called iterations. However, DSDM’s distinct feature is its strong focus on involving stakeholders and ensuring that they are actively engaged throughout the project, much like a tour guide keeping travelers engaged and informed on a trip.

Moreover, DSDM requires that all project decisions are reversible. Think of it like having a flexible plane ticket during your trip, where you can change your next destination until the last moment if you discover a better option.

In terms of structure, DSDM is like building with Lego blocks. Each iteration builds on the previous one, but adjustments can be made along the way to better fit the end goal, ensuring that the project always aligns with what the business needs, similar to how you might adjust your travel itinerary to make sure everyone has the best experience possible.

Overall, DSDM is about being thorough and structured like Waterfall, yet flexible and iterative like Scrum, providing a robust framework that helps teams deliver effective, tailored software solutions.

Rapid Application Development is a software development approach designed to offer quick and efficient results. Think of it as cooking a meal using a microwave instead of a slow cooker. It's all about speed and getting things done faster by shortening the development time.

RAD works through rapid prototyping, which is akin to sketching out a drawing before painting the final picture. Instead of spending a lot of time planning every detail upfront, teams quickly create prototypes of software applications. These prototypes are functional versions of the software that aren't fully polished. They're shown to users to get feedback, and this feedback is used immediately to make quick revisions or improvements. This loop of prototyping, feedback, and revisions continues until a satisfactory version is developed.

Comparing RAD to other methodologies like the Waterfall model, RAD is much less linear and more flexible. In Waterfall, you finish one phase completely before moving on to the next, like completing all the drawings for a house before starting to build. In RAD, however, you'd start building a room, get feedback, tweak the design, and then proceed to the next room, revising as you go based on immediate feedback and changing needs.

When compared to the Dynamic Systems Development Method (DSDM), another agile framework, both prioritize flexibility and user involvement, but they approach it differently. While RAD focuses on quick iterations through prototyping, DSDM integrates more structured planning and user involvement throughout the entire process. DSDM ensures that every aspect of the project aligns with business needs from start to finish and includes more defined roles and phases than RAD, which is more informal and adapts quickly at the expense of less initial planning.

After finishing the list of SDLC models with a few leftovers, we can wrap up with an overview of the V-Model and Spiral Model, two distinct approaches to software development.

V-Model: The V-Model is essentially an extension of the Waterfall model, structured in a V-shape where each development phase is linked to a corresponding testing phase. It's highly systematic, with clear deliverables at each stage, making it suitable for projects with fixed requirements and minimal changes expected.

Spiral Model: Conversely, the Spiral model emphasizes iterative development, where each spiral loop allows for incremental refinement based on risk analysis and client feedback. This model is adaptable and particularly effective for complex, risk-laden projects that may require ongoing adjustments.

Comparison:

• The V-Model is preferred for its clarity and predictability in projects where requirements are unlikely to change.
• The Spiral Model excels in environments where flexibility and iterative evaluation are necessary to accommodate evolving project needs.

Summary:

To choose the most suitable SDLC model from the list we covered, it's essential to consider various factors such as project requirements, team size, risk tolerance, development speed, and customer involvement. Here's a structured guide to help you decide:

Identify Project Requirements:

• Clarity and Stability: If your project requirements are well-defined and unlikely to change, consider Waterfall or V-Model.
• Dynamic and Evolving: If your project is expected to evolve or if requirements are unclear from the start, opt for Agile, Scrum, XP (Extreme Programming), or Spiral.

Consider Team and Organizational Structure:

• Small Teams: For small teams, methods like Scrum, XP, or Kanban work well.
• Large Teams or Enterprises: For larger teams or enterprise-level projects, consider Scaled Agile, LeSS (Large Scale Scrum), Scrum at Scale, or Spotify Model.

Assess Customer Involvement:

• High Customer Involvement: If frequent feedback and continuous customer interaction are vital, Agile, Scrum, or XP are suitable choices.
• Limited Customer Interaction: Models like Waterfall or V-Model may be appropriate when customer interaction can be scheduled at specific milestones.

Analyze Risk and Flexibility Needs:

• High Risk and Need for Flexibility: If your project is complex and requires risk assessment throughout its development, consider Spiral or RAD (Rapid Application Development).
• Moderate Flexibility: If you need some flexibility but with a structured approach, Scrumban (a mix of Scrum and Kanban) or Dynamic Systems Development Method (DSDM) could be ideal.

Focus on Specific Attributes:

• Security Focus: If security is a paramount concern from the start, MS Security Development Lifecycle (SDL) should be your go-to model.
• Feature Specific: If the project is to be broken down into specific, valuable features for the client, Feature-Driven Development (FDD) is a good choice.

Evaluate Development Speed:

• Quick Development: For projects that need to be developed rapidly, RAD or XP offer frameworks that facilitate fast-paced development cycles.

Prioritize Organizational Culture:

• Cultural Fit: Consider models like the Spotify Model if promoting autonomy and a strong organizational culture aligns with your company’s values.

Consider Project Size and Complexity:

• Large, Complex Projects: For larger, more complex projects, consider Spiral, Scrum at Scale, or LeSS.

Final touch:

To be honest, diving deep into these SDLC models was both fun and more challenging than I expected! I thoroughly enjoyed the process, though, and I hope it proves just as useful to you. And if you haven't checked out the album I shared, I advise you to listen to it while you ponder these methodologies, check out, "Diary of Dreams" with the symphonic orchestra it is wick.

P.S. The images accompanying this article are inspired by the geometric shapes and vibrant style of Erik Jones' art prints.

#SDLC #SoftwareDevelopment #Agile #Scrum #TechTalk #SoftwareEngineering #LateNightThoughts #DiaryOfDreams #ErikJonesArt