7 ways ColdFusion projects fail

TeraTech - The ColdFusion paramedics and specialists

1www.teratech.com 1/36

7 ways CF projects fail

(and how to solve issues for success)

Michael Smith, TeraTech, [email protected]://www.teratech.com

301-424-3903 x110Copyright TeraTech 2013



Overview• What is a project?• 7 ways ColdFusion projects fail

Scope creep and requirementsBuggy peoplewareLack of user/executive supportPoor planning and milestonesNo vision and objectivesIncompetent StaffPoor testing and deployment

• Q&A



Speaker Information

• Michael Smith

• 37 years programming,16 CF

• CEO of TeraTechThe ColdFusion paramedics and

specialists



What is a project?• has beginning• has an end• takes resources

people/timemoneyequipmentlocation/deskresource use is temporary



What is same for all Projects?

• Each project is different in details but all share common elements.Visualize

• Project expectations

Plan• Tasks and dependencies

Implement• Develop, test, deploy

Close• Lessons learned



Definition of Project Success

“success equals met expectations”



7 ways ColdFusion projects fail

• Scope creep and requirements

• Buggy peopleware

• Lack of user/executive support

• Poor planning and milestones

• No vision and objectives

• Incompetent Staff

• Poor testing and deployment



1a. Scope creep and requirements

• IssuesScope changes during projectUsers can’t express their needsLate delivery and budget overrunsEndless changes reduces code quality



1b. Scope creep and requirements

• SolutionsClear written requirements, including mock

ups of screens and reportsFormal Sign offFormal change request system



2a. Buggy peopleware

• Peopleware = Political and social issues in software development

• IssuesLow developer productivityPoor teamworkBad group dynamics



2b. Buggy peopleware

• SolutionsHire smart people and trust themPrivate offices and windows.team aligned goals and limit non-team work. Manager: protect from execs and corp politics help developers "flow“ – remove interruptionsattack cubicles, dress codes, telephones, bad

hiring policies, and company core hours



3a. Lack of user/executive support

• IssuesCan’t get decisions made (or made early!)Turf wars unresolvedshelfware



3b. Lack of user/executive support

• SolutionsGet buy in of senior exec project championInvolve users in prototyping and UI

reviewsOrg. change psychology /motivation



4a. Poor planning and milestones

• IssuesResource contentionWe are “90% done” all the timeLack of milestones and versioning



4b. Poor planning and milestones

• SolutionsTask list (no big tasks)Make estimatesKey Resource allocationPM software



5a. No vision and objectives

• IssuesDon’t know where we are goingDon’t know if we have arrivedTeam members going in different

directions



5b. No vision and objectives

• SolutionsClear written vision up front

• a few sentences describing the project

• Business reasons and value

List goals to measure success• Expected results, prioritized

• S.M.A.R.T. goals

Assumptions listed



Benefits of Project Vision

• common understanding of projectbetween client and youhelps explain what project is about

• know when you are done• defines general scope of project

avoid doing things that are not in the project

• get people enthusiastic about projecthelp get project startedhelp see past obstacles



6a. Incompetent Staff

• IssuesGreat variance in developer productivityCreate more problems than they solveDemoralize other team membersTurnover costs



6b. Incompetent Staff

• SolutionsBetter hiring practicesKeep poor performance off your team

• Or assign to “safe” tasks

Keep good teams together for future projects



7a. Poor testing and deployment

• IssuesBugs show up in productionSlow performance with real data volumesServer crashes under load



7b. Poor testing and deployment

• SolutionsAcceptance testing period, Test planCode review Staging serverAutomated deployment scriptsLoad testing, Server tuning



Risk reduction

• IssuesSurprise issues delay projectDBA not available at key timeDependencies

• SolutionsRisk analysis and mitigationsRegular risks reviewDependencies chart



Project Success Factors

The CHAOS Report , Standish Group

Project Success Factors

1. User Involvement

2. Executive Management Support

3. Clear Statement of Requirements

4. Proper Planning

5. Realistic Expectations

6. Smaller Project Milestones

7. Competent Staff

8. Ow nership

9. Clear Vision & Objectives

10. Hard-Working, Focused Staff



What Good PM achieves

• Reduce risks

• Fulfill client expectations

• Complete in budget and on time



Books

• “The Mythical Man-Month” by Frederick Brooks

• “Rapid Development” by Steve McConnell• “Software Project Survival Guide” by

Steve McConnell• “Peopleware” by Tom Demarco, et al• “Controlling Software Projects:

Management, Measurement, and Estimates” by Tom Demarco and Barry Boehm



The choice is yours

Go from project failure

To project success



Project Check up

• Are you are interested in a TeraTech project check up?Project failure risk analysisSecurity and hacker proofingServer optimization and tuningCode review

Email [email protected] for details



Q&A

Thanks for attending!

Enter Questions in the question window (not the chat)

Technology

7 ways ColdFusion projects fail