Email Alerts
-
Software defects increase cost of Agile projects
Fixing software defects can increase the cost of Agile software development projects, according to a recent voke inc. survey. Feature
-
Agile for data warehousing and business intelligence applications
Find out how development of business intelligence and data warehousing applications differ from traditional application development, and how Agile principles and techniques can still be applied. Feature
-
Agile methodology adoption in decline
In this story, Crystal Bedell reports on findings from the SSQ reader survey and discusses the challenges readers are experiencing with Agile adoption. Feature
-
Five ways to kill Agile development adoption and projects
Agile development veterans cite the most common mistakes they see being made in Agile adoption and implementation. Feature
-
Agile problem areas that pain developers and testers
Developers and testers find problems with Agile including required meetings, inadequate documentation and issues related to short iterations. Feature
-
Agile backlash series: Exploring Agile development problems and solutions
Experienced Agile testers and developers discuss development problems that cause backlash. Tutorial
-
Addressing software quality issues with development models, methods
Each software development model has its own practices for building quality software. It is up to software makers to determine which model best fits their needs and to follow its practices so that they can deliver software on time that meets users' ne... Learning Guide
-
Agile Manifesto interpretations: The importance of individuals and interactions
Couched in terms of Agile development, Howard and Rogers explore the importance of strong leadership, communication, collaboration and teamwork using techniques such as self-directed teams and DISC analysis to understand communication styles in their... News | 14 Nov 2011
-
Agile testing success with Janet Gregory
How has Agile testing changed over the past 10 years and what are the most important skills for an Agile tester? These are two of the questions that are explored in this interview between Lisa Crispin and Janet Gregory, co-authors of, "Agile Testing ... News | 27 Apr 2011
-
Trends in ALM: Requirements management tools
Requirements management continues to be a challenge to software development organizations, but tool vendors are working to address those challenges. In this interview with Forrester analyst Mary Gerush, we hear about five important ALM trends in requ... News | 22 Mar 2011
-
Agile software development: What fuels the fire for some burns the house down for others
The Agile software development model is responsible for numerous project successes, speeding up delivery and building strong developer/tester partnerships, but the methodology of choice is not without its enemies. Article | 23 Aug 2010
-
Waterfall destined for the guillotine as IBM appoints Agile its standard
Surprisingly, many IBM Innovate 2010 speakers, including Walker Royce, spoke out against waterfall and other "dated" methodologies and put their full support behind lean and agile approaches to software development. News | 15 Jun 2010
-
Expanded focus at IBM Innovate 2010; ALM, Rational and Jazz
For 2010, IBM is planning to expand its Innovate conference focus beyond its Rational suite of software products in an effort improve business systems from within. ALM tooling and products built on the Jazz platform will also be represented this year... Article | 02 Jun 2010
-
Where Agile development works and where it doesn't: A user story
Agile development is continuing to gain momentum in the software development industry, for British Airways, whom recently joined the agile ranks, there are still areas where waterfall is their preferred methodology. Article | 24 Feb 2010
-
The Agile way, who can do it and who can't?
Agile guru Lisa Crispin explains situations in which agile is the best developmental approach and when it isn't. The decision depends on management style as well as the team's learning curve and willingness to accept the cultural shift agile requires... News | 24 Feb 2010
-
Agile and waterfall neck and neck as business side fails to engage
Lazy business execs and analysts are key barriers to wider adoption of agile development, according to Jon Kern, co-author of the Agile Manifesto and a keynote speaker at the Server Side Java SymposiumInterview | 16 Mar 2009
-
Turning agile skeptics to believers at Blueprint Systems
Blueprint's CTO was skeptical about the powers of agile, especially when it came to distributed teams, but now he's made believers of the whole organization. Article | 11 Mar 2009
- See more News on Traditional Software Models (RUP, V-Model, CMM, Waterfall)
-
Hybrid solutions: When mixing methodologies makes sense
Learn about when and how hybrid solutions can work better rather than a pure agile approach or traditional ones. Tip
-
Agile techniques that your organization can incorporate regardless of methodology
Learn how to incorporate Agile techniques into other development methodologies you may be using. Tip
-
Optimizing requirements management: Working with Agile and Waterfall
Learn what can teams do to optimize requirements management when working within both Agile and Waterfall. Tip
-
Transitioning a Waterfall team to an Agile development team
Agile expert Lisa Crispin offers advice on the steps to take to transition a team from Waterfall to Agile development team. Tip
-
Making the Agile transition: What QA and test managers need to know
Moving from traditional software development to Agile is a major change. Amy Reichert provides the fundamentals to prepare teams for an Agile transition. Tip
-
Ten ways Agile development process, Waterfall approach differ
What makes the Agile development process different from the Waterfall approach? A software development expert exposes 10 important differences. Tip
-
Extending Agile ALM: Why Agile engineering practices matter so much
Agile consultant Howard Deiner explains several Agile engineering practices that can be used regardless of which methodology your organization employs. Tip
-
Beyond burndowns: Metrics for enterprise Agile
Executive management and stakeholders want to know the status of a project and this is traditionally done with metrics. But as our approach to software development changes, so do our measurements. In this tip, find out which metrics consultant Howard... Tip
-
Adopting Agile: Eight traction tips to make Agile development stick
Agile transition isn't easy. The tendency may be to revert back to traditional methods once the going gets tough, though experts encourage organizations to stick with it. In this tip, we learn eight tips for Agile traction recommended by Howard Deine... Tip
-
Waterfall vs. Agile development: A case study
Two projects very similar in scope were executed by the same project team for the same users. The first project used a waterfall methodology and resulted in missed deadlines and failure to deliver user requirements. The second used an Agile methodolo... Tip
- See more Tips on Traditional Software Models (RUP, V-Model, CMM, Waterfall)
-
Applying Agile principles on non-Agile teams
Expert Lisa Crispin describes how teams can apply Agile principles to reach development goals, whether using an Agile, mixed methodology or Waterfall approach. Answer
-
How to improve software product quality with high-functioning teams
Lisa Crispin offers steps high-functioning teams can take to improve software product quality, regardless of methodology. Answer
-
How to employ Agile values with a Waterfall methodology
As Agile development has gained in popularity, the traditional methods such as Waterfall sometimes get a bad rap. However, the two methodologies do not have to be mutually exclusive. Read this response for expert Lisa Crispin’s take on integrating Ag... Answer
-
Software architect involvement in business analysis for waterfall development
There are many advantages to inviting software architects, as well as development and testing experts, to participate in business analysis in waterfall organizations. This expert response explains the business benefits of having key team leads partic... Answer
-
Four tips for gathering requirements for the new Business Analyst
Requirements expert Robin Goldsmith describes four techniques for the new business analyst to collect and analyze business requirements for your software product. Ask the Expert
-
Waterfall versus iterative development misconceptions
Many programmers have an idea of what their finished product should look like but are confused on where to start and how to finish. Development expert describes differences and advantages in waterfall versus iterative software development. Ask the Expert
-
Differentiating between Functional and Nonfunctional Requirements
Many of the difficulties encountered in defining requirements relate to the functional-nonfunctional distinction. As so often happens, some of those difficulties are things of which people are aware, largely realizing after-the-fact that nonfunction... Ask the Expert
-
How to choose a software testing methodology
Choosing the right testing methodology, be it agile, waterfall, V-model or spiral model, depends on the software project, explains expert John Overbaugh. Ask the Expert
-
Varying SDLC methodologies among development teams
Software development life cycle (SDLC) methodologies have their own advantages, tools and so forth. Expert David Christiansen explains why development groups should be allowed to embrace a variety of methodologies. Ask the Expert
-
Is iterative development a new process?
Iterative development, contrary to many people's beliefs, has been around for decades. Expert Bas de Baar reviews how it came into being. Ask the Expert
-
systems development life cycle (SDLC)
The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed applica... Definition
-
SSADM (Structured Systems Analysis & Design Method)
SSADM (Structured Systems Analysis & Design Method) is a widely-used computer application development method in the UK, where its use is often specified as a requirement for government computing projects. Definition
-
Capability Maturity Model (CMM)
The Capability Maturity Model (CMM) is a methodology used to develop and refine an organization's software development process. Definition
-
collaboration diagram
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). The concept is more than a decade old althoug... Definition
-
spiral model (spiral lifecycle model)
The spiral model, also known as the spiral lifecycle model, is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping model and the systems development life cycle (SD... Definition
-
waterfall model
The waterfall model is a popular version of the systems development life cycle model for software engineering. Definition
-
Rational Unified Process (RUP)
Rational Unified Process (RUP) is an object-oriented and Web-enabled program development methodology. Definition
-
rapid application development (RAD)
RAD (rapid application development) is a concept that products can be developed faster and of higher quality through: Gathering requirements using workshops or focus groups Prototyping and early, reiterative user testing of designs The re-use of soft... Definition
-
Software defects increase cost of Agile projects
Fixing software defects can increase the cost of Agile software development projects, according to a recent voke inc. survey. Feature
-
Hybrid solutions: When mixing methodologies makes sense
Learn about when and how hybrid solutions can work better rather than a pure agile approach or traditional ones. Tip
-
Agile techniques that your organization can incorporate regardless of methodology
Learn how to incorporate Agile techniques into other development methodologies you may be using. Tip
-
Optimizing requirements management: Working with Agile and Waterfall
Learn what can teams do to optimize requirements management when working within both Agile and Waterfall. Tip
-
Applying Agile principles on non-Agile teams
Expert Lisa Crispin describes how teams can apply Agile principles to reach development goals, whether using an Agile, mixed methodology or Waterfall approach. Answer
-
How to improve software product quality with high-functioning teams
Lisa Crispin offers steps high-functioning teams can take to improve software product quality, regardless of methodology. Answer
-
Transitioning a Waterfall team to an Agile development team
Agile expert Lisa Crispin offers advice on the steps to take to transition a team from Waterfall to Agile development team. Tip
-
Making the Agile transition: What QA and test managers need to know
Moving from traditional software development to Agile is a major change. Amy Reichert provides the fundamentals to prepare teams for an Agile transition. Tip
-
Ten ways Agile development process, Waterfall approach differ
What makes the Agile development process different from the Waterfall approach? A software development expert exposes 10 important differences. Tip
-
Extending Agile ALM: Why Agile engineering practices matter so much
Agile consultant Howard Deiner explains several Agile engineering practices that can be used regardless of which methodology your organization employs. Tip
- See more All on Traditional Software Models (RUP, V-Model, CMM, Waterfall)
About Traditional Software Models (RUP, V-Model, CMM, Waterfall)
Traditional software development methodologies include waterfall, the V-Model and Rational Unified Process (RUP). The waterfall approach, the most popular of traditional models, is a disciplined, sequential approach to software development. The lifecycle starts with a requirements phase resulting in a requirements specification. Development continues with design, implementation, verification, and maintenance, with rigid criteria that must be met before continuing to the next phase. The V-model can be thought of as an extension of the waterfall, mapping test phases to the phases of the development cycle. RUP is an adaptable process framework allowing organizations to select elements of processes that are most relevant for their project.