Current Articles | | Search | Subscribe (RSS)

Entries for the 'Requirements Management and Communication (BABOK KA)' Category

» Managing Process Architecture and Requirements in a CMMI® based SPI project

(526 Views) (0 Comments)

When developing or changing a process, and all its related assets, often the process engineers have to face an important issue: how defining an integrated set of processes so that each process element is designed taking in consideration its relationships with all the other interfacing elements. Together with this issue, we also have the need to ens...

» Rapid Requirements Engineering – Does a Specification Always Need to Come at the Start?

(572 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...

» FEATURED: Agile Requirements, in Context

(2702 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...

» FEATURED: Developing Requirements in Agile Projects

(2211 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...

» Process Models Bridge the Requirements Gap

(606 Views) (0 Comments)

Defining business requirements accurately is one of the most important success factors for technology projects. Rather than focus on solutions that satisfy a list of requirements, we need to focus on solutions that satisfy desired business outcomes. The best way to achieve this is by performing business process modeling. Employing a vi...

» Best Practices for Agile/Lean Documentation

(876 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

(415 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

(491 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

(732 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

(307 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...

Page 2 of 3

First Previous 1 [2] 3 Next Last

Join the Premier Community for Business Analysts & Systems Analysts!

Business Analyst Articles: Business Analysis & Systems Analysis

Entries for the 'Requirements Management and Communication (BABOK KA)' Category