Project Management
ALL    DOWNLOADS    ARTICLES    REFERENCE    PROCESS    ON-DEMAND WEBINARS   
TRAINING    LIVE WEBINARS    USER-GENERATED
Books    Events    Links    White Papers    Wikis   

Language: All    English    Arabic    French    Japanese    Korean    Portuguese    Romanian    Russian    Spanish   
Access: All    Free    Premium   
Sort By: Newest    Title   

513 items found

Page: 1...... 6 7 8 9 10 11 12 13 14 15 16......52 <prev | next>

Critical Path Analysis

Wiki

An analysis technique used to identify the critical (essential) and non-critical (non-essential) activities associated with a business process or work plan and the amount of float (slack) associated with each activity.

Winning Attitude__ Must For A Leader/Project Management.

Wiki

What determines the project? What attitude should be required? What is knowledge? These all questions always come around our minds but we always roam to get this, I will explain by referring to my project experience.

1%-10% Rule

Wiki

The 1%-10% Rule is used to determine the proper level of detail while breaking down the work of a project. The rule states that the lowest level of activities in the WBS of a project should have a duration no less than 1% of the project duration and not more than 10% of the project duration.

MoSCoW Requirements

Wiki

All requirements are important, but they are prioritized to deliver the greatest and most immediate business benefits early. Developers will initially try to deliver all the Must have, Should have and Could have requirements but the Should and Could requirements will be the first to be removed if the delivery timescale looks threatened.

Extreme Programming

Wiki

Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted.

Kano model

Wiki

The Kano model is a theory for product development and customer satisfaction developed in the 1980s by Professor Noriaki Kano, which classifies customer preferences into five categories.

ADVERTISEMENT

Page: 1...... 6 7 8 9 10 11 12 13 14 15 16......52 <prev | next>

ADVERTISEMENTS

"In Italy for thirty years under the Borgias they had warfare, terror, murder, bloodshed - but they produced Michelangelo, Leonardo da Vinci, and the Renaissance. In Switzerland they had brotherly love, 500 years of democracy and peace, and what did that produce? The cuckoo clock."

- Orson Welles, The Third Man

ADVERTISEMENT

Sponsors