If you don't get users involved early in the project, you risk ending up with shelfware. That means that you wrote some great code, the operation was a success but the patient died on the table. None of the users want to use the application and it's left on the shelf. What can you do about this?
Some of the keys to successful projects are getting
· executive support
· having a project champion
· early user buy-in
· early usability testing
Michael Smith is the founder and CEO of TeraTech, a private custom software development company. Since Michael founded it in 1989, TeraTech has become the ColdFusion specialist company:
“Custom ColdFusion apps on budget and on time, guaranteed.”
He has been programming and managing projects for over thirty-five years.
Michael has used ColdFusion since version 1.5 in 1997 and has advanced the ColdFusion developer community:
· Presented at over 50 conferences and user group meetings,
· Written over 20 articles on ColdFusion software development,
· Founded the highly successful CFUnited Conference which ran for 11 years with up to 900 attendees annually, and
· Ran the Maryland ColdFusion User Group for 12 years.
Reach him at michael (at) teratech.com, www.teratech.com or +1 (301) 424 3903 x110.
Connect with Michael on LinkedIn http://www.linkedin.com/in/abundantmichael.
Register to the webinar:
Last Name*Email*Company*No. of Employees*
Job TitleStreetCityStateZip CodeCountryPhoneWebsiteQuestions & CommentsMailingListJuly webinar 2014Webinar
And to continue learning how to make your ColdFusion apps more modern and alive, I encourage you to download our free ColdFusion Alive Best Practices Checklist.
Because… perhaps you are responsible for a mission-critical or revenue-generating CF application that you don’t trust 100%, where implementing new features is a painful ad-hoc process with slow turnaround even for simple requests.
What if you have no contingency plan for a sudden developer departure or a server outage? Perhaps every time a new freelancer works on your site, something breaks. Or your application availability, security, and reliability are poor.
And if you are depending on ColdFusion for your job, then you can’t afford to let your CF development methods die on the vine.
You’re making a high-stakes bet that everything is going to be OK using the same old app creation ways in that one language — forever.
All it would take is for your fellow CF developer to quit or for your CIO to decide to leave the (falsely) perceived sinking ship of CFML and you could lose everything—your project, your hard-won CF skills, and possibly even your job.
Luckily, there are a number of simple, logical steps you can take now to protect yourself from these obvious risks.
No Brainer ColdFusion Best Practices to Ensure You Thrive No Matter What Happens Next
Modern ColdFusion development best practices that reduce stress, inefficiency, project lifecycle costs while simultaneously increasing project velocity and innovation.
√ Easily create a consistent server architecture across development, testing, and production
√ A modern test environment to prevent bugs from spreading
√ Automated continuous integration tools that work well with CF
√ A portable development environment baked into your codebase… for free!
Learn about these and many more strategies in our free ColdFusion Alive Best Practices Checklist.