Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Stan Rifkin

dblp:71/5694 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2000
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 100%

Topics — the 2 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
software project management
0.012000
When the project absolutely must get done: marrying the organization chart with the precedence diagram · ICSE 2000
Empirical software engineering › software project management
software project scheduling
0.012000
When the project absolutely must get done: marrying the organization chart with the precedence diagram · ICSE 2000

Methods — techniques the papers use, named apart from their topics

simulation · 0.0
YearPublicationVenuePosition
2000 When the project absolutely must get done: marrying the organization chart with the precedence diagram
abstract
Very little is new in project planning, but this is! We present a technique to marry the organization chart with a project's task precedence diagram. This permits us to simulate the project at a micro, project-specific level never before achieved. We can perform “what-if” scenarios related to organization structures, the deployment of specific individuals and skills, and the structure of information flow and exception-handling in a project. The tool used, ViteProject, was developed over the last ten years in a Stanford University laboratory, where substantial results have been achieved when applied to design activities other than software. We present our real-world experience with several software projects, where it has improved project visibility and allowed us to rationally optimize projects in a way hitherto impossible.
Stan Rifkin
ICSE1