What is a Software development methodology?

A software development methodology or system development methodology in software engineering is a framework that is used to structure, plan, and control the process of developing an information system.

What Is Rapid Application Development (RAD)? by susan de sousa

RAD or Rapid Application Development is designed to deliver software at a faster pace than would be possible with the traditional waterfall model.

RAD places less emphasis on planning and ...

The V-Shaped Software Development Life Cycle by raymond lewallen

The V-Shaped SDLC is sequential and each phase is completed before the next phase begins.

Testing is emphasized in the V-Shaped model. The testing procedures are developed early in the ...

How does kanban compare to test driven development? by kent beck

The goal of kanban is to increase the value of a production process.

Kanban increases the feedback in production by limiting the amount of work in progress at any one ...

Select the Right Model for Your Project by johanna rothman

Serial lifecycles, characterized by waterfall and Agile lifecycles, characterized by Scrum are not the only two choices when it comes to software development life cycles (SDLC).

There are several more lifecycles ...

The Waterfall Software Development Process by jim rising

Waterfall is so named because of the way that it's phases flow downward, similar to an actual waterfall.

It is best used for projects where the requirements are clearly stated ...

Pros and Cons of Blended Waterfall / Agile Software Development

Thirty-five percent of developers surveyed by Forrester in late 2009 said they were using agile development.

31 percent said they don't follow a software methodology at all meaning they may ...

A History of the Waterfall Software Development Model by omkar phatak

The Waterfall software development model was formally introduced in a paper published by Winston Royce in 1970.

Winston Royce introduced Waterfall as a flawed method of software development, that is ...

An Introduction To Iterative & Incremental Software Development by ian spence

Iterative and incremental development requires project managers to consider each iteration as a separate project, to be managed in the context of the final deliverable.

An iteration creates a demonstrable, ...

The Principles of Lean Software Development by przemysław bielicki

Lean Software Development helps software organizations optimize their software development processes so they can deliver their products to market faster and with better quality.

Lean software development aims to fix ...

What is Lean Software Development (LSD)? by darrell norton

According to the National Institute of Standards and Technology Manufacturing Extensions Partnership’s Lean Network, Lean is:

1. A systematic approach to identifying and eliminating waste through continuous improvement, flowing the product ...

Kanban Cards for Lean Software Development (LSD) by karl scotland

Kanban is a concept related to lean and just-in-time (JIT) production.

According to Taiichi Ohno, the man credited with developing Just-in-time, kanban is one means through which JIT is achieved.

The ...

The Unified Process (UP) and Rational Unified Process (RUP) by sinan si alhir

The Unified Process (UP) is a use-case-driven, iterative and incremental development process framework that utilizes the Object Management Group's (OMG) Unified Modeling Language (UML).

UP is useful in both small-scale ...

How Customer Feedback Improves Agile Software Development by eric peters

In Agile software development, feedback loops play an important role in improving the quality or process of software development.

As a software development / project team, you deploy your software application ...

10 Key Principles of Agile Development by kelly waters

The 10 Key Principles of Agile Software Development:

1. Active user involvement is imperative

2. The team must be empowered to make decisions

3. Requirements evolve but the timescale is fixed

4. Capture requirements ...

Why Agile or Scrum Works Better For Web User Experience by patrick neeman

While Agile development does not guarantee business breakthroughs, it removes the development process as a risk and also helps with delivering a better user experience!

Here are seven (7) principles that ...

The Pitfalls of Agile Project Management by jesse fewell

If your project is small, simple and low-risk then the overhead of an Agile Project may not be worth it.

Because of the planning (daily, iteration, release, project) and processes ...

Developing A Strategic Agile Philosophy by george dinwiddie

Learn the necessary technology skills iwhile accomplishing some real work.

The initial backlog really only needs to be one item in order to start delivering.

Learn the parts that aid ...

Agile Software Development Flattens Traditional Effort or Cost Curves by scott bellware

The cost of software development (changing existing features or adding new features) gets exponentially higher as a project progresses.

Agile software development does not allow the efforts to spiral toward ...

The most important or difficult task in software development is? by kirk knoernschild

The difficulty in software development is not writing code or applying a certain technology stack. Instead, the challenge lies in the specification and design of the software itself.

Therein lies ...

12 Best Practices for User Experience (UX) Design in an Agile Environment by jared spool

In the "old" waterfall method of development, there are explicit milestones: first you develop requirements, then you create a design that meets those requirements, then you lay out the functionality ...

Why The Customer Is King on Agile Projects by jason gorman

The weekly, bi-weekly or monthly "show-and-tell" is one of the customer's most powerful weapons.

As a customer, you're holding most of the planning cards, too.

If you choose to change ...

Agile Means Simple Things Done Well, Not Complex Things Done Fast by eric brown

We spend too much time complicating our lives by trying to do too much, too fast!

There seems to never be enough time to do something correctly, but always enough ...

An Introduction To Agile and Scrum Methodologies

In 2001 agile was formalized by 17 pioneers at the Snowbird Ski Resort in Utah and the famous Agile Manifesto was born.

The Agile Manifesto is a foundation for agile ...

Misunderstanding Scrum and Waterfall by venkatesh krishnamurthy

Waterfall tends to view people as assignable, parsed, optimized resources while scrum sees treats people as creative, self organizing and directing and capable of complex work.

While waterfall treats work ...

Self Organizing Teams Are Indispensable To Scrum! by ken schwaber

Self organizing teams is one of the core concepts of Scrum and it makes Scrum unique compared to other methods / frameworks.

Scrum emphasizes teamwork and self organizing high skilled ...

So, what is a product burn down chat in Scrum? by peter stevens

Scrum and XP differ from other frameworks in the use of a burn down chart rather than milestones to measure progress.

A product burn down chart tracks the amount of ...

Agile Processes Improve Estimation, Prediction and Empower Commitments by scott sehlhorst

Agile processes are designed to help you deliver what your customer actually needs, not what was originally asked for.

In Scrum, you estimate a collection of user stories – ...

What do you really care about in Scrum? by ron jeffrie

SCRUM helps you to ship running, tested software every two weeks or every month.

SCRUM helps you review how your project is going and make frequent adjustments that help you ...

Why Story Points Are Better Than Hours for Estimating by sammy larbi larbi

Story points are better than hours for estimaing because:

We are bad at estimating hours, but more consistent with points

Hours tell us nothing since the best developer on the team may ...

Extreme Programming (XP) Explained by artem marchenko

Extreme Programming or XP is a well known agile software development method.

XP is a catalog of good practices exploited to the "extreme" level.

It is guided by five values, fourteen ...

Evolutionary Design In Extreme Programming (XP) by martin fowler

Evolutionary Design (XP) advocates evolutionary design methods in the place of planned design.

Extreme Programming (XP) rejects significant effort in up-front design, in favor of a more evolutionary approach.

Evolutionary design means ...

What is a user story in agile / extreme programming (XP)? by jack milunsky

A user story consists of ...

Card

Conversation

Confirmation

Card:

User stories are written on cards. The card does not contain all the information that makes up the requirement.

Instead, the card has just enough ...