Latest Posts

Facilitated Application Specification Techniques (FAST)
Facilitated Application Specification Techniques (FAST)

FAST is similar enough to brainstorming and to JAD that we will provide only cursory coverage here. This is not to belittle the process in any way - FAST is an important part of the software PM's vocabulary because it was developed to be a method particularly for gathering software

Tags fast, brainstorming, jad, software requirements, elicitation methods

Requirements Elicitation Methods
Requirements Elicitation Methods

We will study interviewing, brainstorming, mind mapping, facilitated application specification technique (FAST), Joint Application Design (JAD), and use case scenarios as viable methods for eliciting software requirements. These are some suggested activities and thoughts that are

Tags software requirements, fast, jad, brainstorming, mind mapping

What Is a Software Requirement
What Is a Software Requirement

A software requirement is a capability that somebody needs or wants. It can be a component of an entire new application, a new feature for an existing application (an enhancement), or a request to correct a current shortcoming. IEEE describes a requirement as: (a) a condition or capability needed by a user to solve a problem or achieve an objective; (b) a condition or

Tags software requirement, product features, requirements elicitation

Requirements Management and the SEI CMM
Requirements Management and the SEI CMM

Requirements management is a key process area (KPA) for SEI CMM Level 2, the repeatable level. The purpose is to "establish a common understanding between the customer and the software project of the customer's requirements that will be addressed by the software project."

Tags software product, life cycle, software engineering group, software project, csf

Background for Requirements Management
Background for Requirements Management

A number of excellent guides to requirements elicitation have been published; therefore, our intention is not to rearticulate them, but to make the reader aware of them and the power of their use. Gerald Weinberg, Roger Pressman, and Barry Boehm have suggested steps to gather

Tags software system, software requirements, requirements engineering, requirements elicitation

Eliciting Requirements
Eliciting Requirements

Almost everyone involved in software engineering or software project management during the last 20 years is well aware of the importance of requirements. We rarely hear of a success story declaring victory over the ever-elusive set of specs, but we often hear poor requirements

Tags life cycle, software product, software project management

Critical Chain Scheduling
Critical Chain Scheduling

Up to now, we have talked only about the classical project management scheduling techniques (PERT, CPM, PDM, etc). Now that you have grounding in what "classical PM" is all about, let's consider some recent thinking in the scheduling field. Since the 1950s when PERT and CPM

Tags toc, buffer sizing, project schedule, chain schedule

Map the Schedule to a Real Calendar
Map the Schedule to a Real Calendar

One of the things that seems to confuse most new project managers is how to build a workable schedule. Often, since they know they want a Gantt chart when they are done (because they saw one in a management review once), they start with that view of their WBS in a scheduling

Tags gantt chart, scheduling software, leveling algorithm

Leveling Resource Assignments
Leveling Resource Assignments

When all the resources (Assigning Resources) have been allocated to the scheduled and precedence-linked (Considering Dependencies) activities from the WBS (Creating the Work Breakdown Structure), and the activity-constrained schedule is prepared, the resource

Tags resource overloads, scheduling algorithm.scheduling tools

PERT and CPM Scheduling
PERT and CPM Scheduling

These two methods of schedule analysis have been around since the 1950s, and form the foundation of what the profession knows about scheduling today. CPM (critical path method) was developed by DuPont in 195859, and uses fixed-time estimates for each activity. PERT

Tags beta distribution, triangular distribution, schedule analysis, gantt chart, scheduling

The contents available on this website are copyrighted by TechPlus unless otherwise indicated. All rights are reserved by TechPlus, and content may not be reproduced, published, or transferred in any form or by any means, except with the prior written permission of TechPlus.
Copyright 2015 SPMInfoBlog.
Designed by TechPlus.com.pk