Articles tagged with: Schedule
Just how much can people factors influence your project cost and effort? 24.6 percent! In other words, the least experienced team (the bottom 15 percent) can require up to 24.6 times as much effort to complete a project as the most experienced team (top 10 percent.) In Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers, Steve McConnell writes about the Cocomo II model and how personnel factors influence project cost and effort.
The Cocomo II ModelHow much do personnel factors influence the project’s cost and effort …
Adding people to late projects makes them later. This can be counter-intuitive. In Requirements-Led Project Management: Discovering David’s Slingshot, by Suzanne Robertson and James Robertson explain how adding people to late projects makes them later.
The Least Knowledgeable People Prevent the Most Knowledgeable People from WorkingAccording to Suzanne and James, adding people to a late project, makes the project later:
The problem of adding people means disrupting the rhythm that your existing team has established. It increases the number of communication paths. New people penalize the existing team. When new members arrive, …
How do you know when you’re signing up for Mission Impossible? If your project has a short time frame to design, build, and deliver, and there’s high risk around the requirements and technology, there’s a good chance your project scenario is Mission Impossible. In Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle, Ian F. Alexander and Neil Maiden write about Mission Impossible scenarios.
Alexander and Maiden show a table that summarizes the project situation:
Is there a business need to get the product to market in the shortest time possible?
Evolutionary, Incremental, and High-Risk are software process models for systems engineering ‘in the large’. In the Evolutionary model, the complete cycle of activities is repeated for each version. In the Incremental model, increments are individually designed, tested, and delivered at successive points in time. In the high-risk model, the project is divided into phases and each phase helps constrain risk. In Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle, Ian F. Alexander and Neil Maiden write about the Evolutionary, Incremental, and High-Risk software process models for systems engineering ‘in …