Ft

Slide1: 

Project Monitor, Forum and Billing Systems An integrated solution for your business company. Developed and designed by FuelTooler.com

Slide2: 

Overview Our Solution Project Monitor Software Billing System Module Forums System Conclusion Content

Slide3: 

Problem:: Historic failure of IT Projects Exact % failure 'unkown' but it ranges from 50-75% Various reasons identified Various samples shown Common people see IT Projects and IT Departments as isolated or outside the real world. Overview

Slide4: 

Main problems: Unrealistic time frames Over budget Unclear requirements, poorly defined Project specifications and scope, lack of clear vision and objectives Failure to involve users and their expectations Failure to manage the change required. Lack of adequate management support Inadequate attention to project momentum, harmony and rhythm Solutions: User involvement Dedicated and talented staff Proper planning, good project management Learning from mistakes Overview

Slide5: 

How common people see IT projects?

Slide6: 

How common people see IT projects?

Slide7: 

We concentrate on the solutions presented above: Competent staff Great management User involvement At FuelTooler, we proudly present three basic components so as to solve the majority of the problems: Project Monitor Software Forum Systems Billing System Module Our Solution

Slide8: 

Major involvement from everyone. More possibilities to communicate. Customer’s input is real. Ongoing process. On real time. Adjustments, errors, changes. No surprises. Project Monitor

Slide9: 

Fluid communication. Everyone involved. Stays there for future reference. No lost emails. New people can be included at any time. Forum System

Slide10: 

Customer – Leader- Worker Billed exact ammount of work. Customer knows what to expect. Billing System

Slide11: 

Demo

Slide12: 

At FuelTooler, we tackle historic problems and we reinforce methodologies that did work in the past: Proactive company All details are looked at No loose ends Proper management and leading Everything done in clear stages Conclusion

Slide13: 

Why IT Projects Fail http://zones.advisor.com/doc/16379 Why do Projects Fail? http://www.jiscinfonet.ac.uk/InfoKits/project-management/pm-intro-1.2 Borland University Looks to Spring Debut http://www.idevnews.com/PrintVersion.asp?ID=153 Why Technical Projects Fail: Avoiding Disaster http://www.stratpartners.com/Why_Technical_Projects_Fail_2.1b.pdf Failed IT Projects (The Human Factor) - Sheila Wilson http://faculty.ed.umuc.edu/~meinkej/inss690/wilson.htm Nightmare on Project X - Restoring Projects in Crisis - by Deb Jacobs http://www.omahaspin.org/slide/200009nightmare.pdf A 50% Data Warehouse Failure Rate is Nothing New http://java.ittoolbox.com/blogs/featuredentry.asp?i=4669 Bibliography / Reference

Slide14: 

Appendix A Ex 1: 'Why IT Projects Fail' (http://zones.advisor.com/doc/16379) '…study by Info-Tech Research Group finds…shows that 95 % of IT departments are not delivering some projects on time or to the full satisfaction of business executives. The study also finds that only 11 percent of enterprises see technology as a 'strategic weapon.' Top three reasons projects fail are: Unrealistic time frames (68 percent) Lack of number of staff (64 percent) Poorly defined project scope (62 percent) Solutions: User involvement Dedicated staff Making sure you have the talent Practicing sound project management Learning from mistakes

Slide15: 

Appendix B Ex 2: 'Why do Projects Fail? http://www.jiscinfonet.ac.uk/InfoKits/project-management/pm-intro-1.2 Most failures have been put down to: Poor project specification Unrealistic timescales Timescales that are too long Inappropriate staff Failure to manage user expectations Failure to manage the change required.

Slide16: 

Ex 3: Integration Developers News 'Borland University Looks to Spring Debut' (2/2/2005) http://www.idevnews.com/PrintVersion.asp?ID=153 '…Borland execs point to The Standish Group's latest CHAOS report (November 2004), which found a sobering 28% of all IT projects succeed.' '…most IT projects (51%) are what the research group called 'challenged' which means one of four things: The project was either seriously late, over budget, missing some of the key features that were expected to be included, all of the above! Appendix C

Slide17: 

Ex 4: 'Why Technical Projects Fail: Avoiding Disaster ' by Glenn P. Kessler http://www.stratpartners.com/Why_Technical_Projects_Fail_2.1b.pdf Technical projects (small, medium and large) 16% were fully successful. (on time, within budget, full requirements.) Nearly 53% were 'challenged' or completed unsuccessfully. The average cost overrun was 189%. The average time overrun was 222%. Overall, only 61% of their required features were delivered. 31%, was cancelled at some point in the development cycle. Appendix D

Slide18: 

Ex 4: 'Why Technical Projects Fail: Avoiding Disaster ' (Cont.) Violations Lack of adequate user input and involvement in the project Lack of sustained executive management support Unclear requirements Lack of proper planning Lack of clear vision andamp; objectives Inadequate attention to project momentum, harmony and rhythm Appendix D (CONT.)

Slide19: 

Ex 5: 'Failed IT Projects (The Human Factor)' by Sheila Wilson http://faculty.ed.umuc.edu/~meinkej/inss690/wilson.htm Success Factors (% of Responses) User Involvement - 15.9% Executive Management Support - 13.9% Clear Statement of Requirements - 13.0% Proper Planning – 9.6% Realistic Expectations - 8.2% Smaller Project Milestones - 7.7% Competent Staff - 7.2% Ownership - 5.3% Clear Vision andamp; Objectives - 2.9% Hard-Working, Focused Staff - 2.4% Other - 13.9% Appendix E