Wednesday, August 27, 2008

Business Analysis Articles & Systems Analysis Articles

Resources


Article Archive


Articles and White Papers


Current Articles | Categories | Search | Subscribe (RSS)

Articles from Agile Methods

» Standing Up for 15 Minutes: Why?
(687 Views) (1 Comments)
The ultimate management sin is to waste people’s time, Tom DeMarco and Timothy Lister told us in their famous book Peopleware [1]. This includes having pointless meetings that prevent people from actually doing anything useful. Nevertheless, some meetings are considered a necessary evil and therefore the so-called “agile movement” in software devel...

» Rapid Requirements Engineering – Does a Specification Always Need to Come at the Start?
(236 Views) (0 Comments)
Requirements and the way they are dealt with are decisive to the success of a project. This statement is never really questioned in modern software engineering circles. Why is it, then, that a systematic requirements engineering (RE) system is so rarely established? Where do the problems lie when it comes to implementing such a system? This p...

» Agile Requirements, in Context
(1649 Views) (0 Comments)
"As I discussed my May article for Modern Analyst, there's a lot of hype about the role of requirements in agile projects. Many people think you don’t “do” requirements on an agile project. Hogwash. Indeed, agile projects use requirements—but just enough requirements at just the right time." In this article Ellen covers a number of agile requireme...

» Developing Requirements in Agile Projects
(1742 Views) (0 Comments)
The latest progression in software development methods is the agile approach. Its growing popularity proves how effective it is. But two extreme—and even dangerous—views have arisen about agile development. One is that you don’t do requirements at all when you’re working on an agile project. The other is that you don’t need good requirements practi...

» Best Practices for Agile/Lean Documentation
(578 Views) (1 Comments)
Ideally, an agile document is just barely good enough, or just barely sufficient, for the situation at hand. Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall projec...

» Agile Requirements Change Management
(272 Views) (0 Comments)
Agile software development teams embrace change, accepting the idea that requirements will evolve throughout a project. Agilists understand that because requirements evolve over time that any early investment in detailed documentation will only be wasted. Instead agilists will do just enough initial requirements envisioning to identify their projec...

» Agile Requirements Best Practices
(309 Views) (0 Comments)
To be honest, I'm not very enamored with the term "best practice". I believe that the term "contextual practice" makes far more sense because what is a "best practice" in some situations proves to be a "worst practice" in others. Having said that, people are interested in best practices so here they are when it comes to agile requirements modeling:...

» Agile Requirements Modeling
(321 Views) (0 Comments)
Many traditional project teams run into trouble when they try to define all of the requirements up front, often the result of a misguided idea that developers will actually read and follow what the requirements document contains. The reality is that the requirements document is usually insufficient, regardless of how much effort goes into it, the r...

» Agile RUP: Experiences from the trenches
(258 Views) (0 Comments)
This article, actually a compilation of three articles, provides proven advice for applying agile strategies on IBM® Rational® Unified Process®, or RUP®, teams. The articles are written by Mark Lines, Joshua Barnes, and Julian Holmes respectively, co-founders of Unified Process Mentors (www.upmentors.com). These three have mentored literally thousa...

» Is the BA an endangered species with the growth of Agile?
(790 Views) (0 Comments)
First, I'm a project focused software developer, team lead, designer, architect, jack of all trades, who has been on projects that have used various methodologies over the years, including of late some agile projects. I'm not a big blog reader, or a big blogger, but like most people I have an opinion on things, and for some reason that opinio...
Previous Page | Next Page
Syndicate  


Privacy Statement  |  Terms Of Use
Copyright 2006-2008 by Modern Analyst Media LLC