Information Technology Projects
Example Project Plans

Professor: Arthur Goldberg
artg <at>

Type of project
Good characteristics
Software purchase Well organized
Good description of the client and their problems
Clear set of requirements
Excellent summary of possible solutions

Were there any other requirements that were abandoned?
Need more of a plan for the rest of the project: what is the schedule? who will work on what? what are the risks?
Analyses of these programs by some third parties would be valuable, although perhaps this will come later or it was not requested.
NYU Stern Report Tool Analysis Transition Report
Software development Good summary of need for 'DemoCentral'
Good list of features, although to provide more detail it could have been broken down into more features (small formatting point -- tables like this look better on a 'landscape' page)
Very good detail on architecture and table design
Superb work on mockups in section "Draft Detailed Designs" -- they clearly define the UI, sections 1.5.2 & 1.5.3 contribute essential information for understanding internals

Could have done quantitative (ROI) analysis of development of Web-based Presentation Management System, but probably not needed.
section 1.6 needs to assign tasks; effort estimates would help convince that tasks could be completed in time available
Extremely good
Wiley Publishing
Software development Good explanation of 'Why is bCorner Search Engine Needed'.

Requirements are insufficient; the 'Features Table' and  'Interfaces' contain far too little detail for a project of this complexity. The 'System Messaging Map', 'ER diagram' and database schema provide needed details, but not enough. The 'Algorithms' are greatly underspecified.
BCorner Transition Report
Software tool evaluation Excellent discussion of project goals, requirements, and deliverables

Superb details throughout: goals, requirements, deliverables, architecture, references to tool documentation, design and sequence diagram, mockups, risk matrix.
Includes a project schedule -- although a MSFT project schedule probably 1) has too many details, 2) predicts the future with a level of accuracy that is not realistic, and 3) requires users to buy software they otherwise wouldn't need, it does help focus the team on scheduling, enumerating tasks, and assigning individual responsibilities. (please do not circulate the zip file, especially the mockups.)

again, while not required, effort estimates might help convince that tasks could be completed in time available
CompanyX report

20transition meeting.doc">