book

Getting Results from Software Development Teams

Name: Getting Results from Software Development Teams
Author: Lawrence J. Peters and Lawrence Peters
ISBN: 9780735623460

by Lawrence J. Peters and Lawrence Peters

April 2008

Beginner to intermediate

304 pages

8h 14m

English

Microsoft Press

Read now

Unlock full access

Dedication
Acknowledgments
Preface
I. The Preliminaries
1. On Software Engineering and Management
The Path to ManagementThe Smart People Got It WrongThe Rest of Us Are Still Getting It WrongThe Functions of ManagementSome Data of InterestHope on the HorizonSummaryReferences
2. Why Is Software So Difficult?
The Nature of the BeastSoftware Development as a “Wicked” ProblemMyths Associated with SoftwareForget About Godzilla—Watch Out for DucksSummaryReferences
II. Software Development as a Process
3. Building the Software Development Team
Team Building as a ProcessConducting InterviewsChecking ReferencesThe Business School ConundrumIt’s DISC TimeThe Apollo SyndromeAshby’s Law and the Ideal Team MemberManagement StylesA Maturity Model for Software Project ManagementMoving from One CMM Level to AnotherTask Maturity LevelsDevelopment Phases and PersonalitiesThe Process of Team BuildingAnother Reason Why Software People Are ChallengingSummaryReferences
4. Developing and Maintaining the Project Plan
The Project CharterThe Software Development PlanAllocating Flow TimeUsing the Work Breakdown StructureDeveloping the WBSUsing Flowcharts, Gantt Charts, PERT Networks, and Rummler-Brache DiagramsFlowchartsGantt ChartsPERT NetworksRummler-Brache DiagramsPerson LoadingOptimizing the Project Plan Using the Design Structure MatrixRisk ManagementSummaryReferences
III. Management Methods and Technology

5. Selecting a Software Development Lifecycle Model: Management Implications
The Software Quality LifecycleViewing Software Development as a ProcessModeling ProcessesDiscovering How to Model ProcessesLifecycle Model BasicsThe Lifecycle ModelsWaterfall ModelSlam Dunk ModelSpiral ModelEvolutionary ModelStage Gate ModelRapid Prototyping ModelAgile Programming ModelSynchronization and Stabilization ModelComparison of Lifecycle Model FeaturesSelecting a Software Development LifecycleSummaryReferences
6. Modeling the Target System
Why Model Software Systems?Requirements Modeling MethodsUsing Dataflow DiagramsUsing IDEF0 to State RequirementsRequirements Analysis Using Self-Interaction MatrixesSystem Response Table (SRT) Specification Method and Real-Time SystemsUse CasesDesign Methods OverviewSelecting Appropriate System-Modeling TechniquesSummaryReferences
7. Estimating Project Size, Cost, and Schedule
Viewing Cost Estimation as a ProcessEstimating Variability as a Function of Project Flow TimeCosting and Sizing Software ProjectsGeneral Form of Schedule Estimation FormulasIBM’s Findings at the Federal Systems DivisionSoftware Lifecycle ManagementFunction Point Estimation MethodOverview of the ProcessAn ExampleAutomated Assistance for Function Point ComputationFunction Points: A Summary3D Function Point MethodData DimensionFunction DimensionControl DimensionComputing Real-Time (3D) Function Point EstimatesPseudocode-Based Estimation MethodCost and Schedule Estimating: An AdvisoryConstructive Cost ModelCOCOMO IIEstimating Development Effort as a Two-Phase ProcessDevelopment Effort EstimatesA Simple ExampleEstimate Adjustments in COCOMO IIDevelopment Schedule EstimatesComputing COCOMO II Scaling FactorsAnother Simple ExampleThe Cost Variance MethodSummaryReferences
8. Tracking the Software Project Plan
Tracking SchemesMaximizing ProfitabilityBeing Task OrientedFinding a Better WayEarned Value ManagementUsing EVM: Terms and FormulasCost-Related FactorsSchedule-Related FactorsWork- and Content-Related ParametersSummary of EVM FactorsApplying EVMEarned ScheduleSummary of EVMPrecedence Diagramming for Cost and Schedule ControlForward PassBackward PassIncorporating FloatFree FloatThe Critical PathCost ModelSchedule and Cost Model CombinedApplying Precedence Diagramming to a Software Development ScheduleTaking Remedial ActionAvoiding Cost and Scheduling Problems in the First InstanceAbout Complexity and Project SuccessSummaryReferences
IV. Managing Software Professionals
9. Improving Team Performance
What Research RevealsMore Recent ResultsThe BasicsHigh-Risk Technical RequirementsHigh-Risk ScheduleStaffingResourcesSoftware QualityThe Relative Importance of the WorkplaceThe Physical WorkplaceThe Relationship WorkplaceWhy People WorkModels of What Motivates PeopleMaslow’s ModelMcClelland’s TheoryExpectancy TheoryGoal Setting TheoryIndividual Characteristics ModelHerzberg’s ModelHow You Can Affect Team PerformanceWhen It All Comes Together or Comes ApartHow Much CMM Is Enough?Managing High-Performance TeamsSummaryReferences
10. Evaluating Software Development Teams
Classic Techniques for Evaluating IndividualsThe Strategy-Based Evaluation MethodUsing SEMThe SEM ProcessSEM—An ExampleTraditional Performance Evaluation Methods vs. SEMEvaluating the Software Development TeamAn Alternative Scheme for Evaluating Software Development TeamsSummaryReferences
A. Lawrence J. Peters
Index
About the Authors
Copyright

404

Not Found

Either this content does not exist or you do not have access to it. Try searching for something new.

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Getting Results from Software Development Teams

by Lawrence J. Peters and Lawrence Peters

404

Not Found