Monday, October 13, 2008
Resources   »   Articles    

Business Analysis Articles & Systems Analysis Articles
Resources


Article Archive


Articles and White Papers

Current Articles | Categories | Search | Subscribe (RSS)


» Best Practices for Agile/Lean Documentation
Article Rating (699 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
Article Rating (323 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
Article Rating (381 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:...

» Requirements Prioritization Introduction
Article Rating (574 Views) (0 Comments)
Once a set of security requirements has been identified, it is often the case that they need to be prioritized. Due to time and budget constraints, it is often difficult to implement all the requirements that have been elicited for a system. It may also be the case that security requirements are implemented in stages, and prioritization can help to...

» Requirements for Outsourcing
Article Rating (249 Views) (0 Comments)
Outsourcing differs from other development because there is bound to be a contractual relationship, probably a geographic distance, a different sense of loyalty, language misunderstandings, cultural differences, reluctance to speak up to the client – and many other associated problems. Good requirements are always a problem, but outsourcing increas...

» IT Pays a Price for Poor Requirements Practices
Article Rating (330 Views) (0 Comments)
IAG Consulting’s new Business Analysis Benchmark makes one thing clear: almost 70 percent of companies surveyed set themselves up for both failure and significantly higher cost in their use of poor requirements practices. That failure came at a significant cost: the average $3 million project cost companies using poor requirements practices an aver...

» Understanding the Specifications Puzzle
Article Rating (1112 Views) (0 Comments)
Defining specifications for the design and development of systems and software is a lot like this classic Gershwin song and what I personally regard as the biggest cause of confusion in the Information Technology field for as long as I can remember, which is over 30 years in the industry.  Some people say specifications should be based on the ...

» Best Practice with Structured Requirements
Article Rating (624 Views) (0 Comments)
Analysts report poor requirements management accounts for as much as 71 percent of software project failures. The main cause is the gap between (a) what the business team wants and how it communicates this, and (b) what IT understands and delivers. No matter how good a project development environment is, if the requirements captured in the first p...
Page 2 of 2First   Previous   1  [2]  Next   Last   
Syndicate  


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