Nobody ever gets to stop and smell the roses in IT. In an article for TechRepublic, Mary Shacklett elaborates on ten techniques to utilize in order to implement “fast IT” without the heightened risk. Maybe you can smell the office plants when you are done.
Techniques that Work
- Use cloud-based tools.
- Document agreements with users for potentially imperfect IT deliverables.
- Split projects into smaller segments.
- Learn to say “no” if need be.
- Do testing offsite.
- Use collaboration.
- Put users on application development.
- Do not accept major enhancements.
- Maybe do not outsource every time.
- Use stable platforms.
In a world that demands fast IT, using cloud-based tools can very much aid in the process. There are many sites in which the entire app infrastructure is already built; all it needs is the business code. Because of this cloudy climate, an overwhelming amount of users are actually comfortable with slightly flawed apps since they are more concerned with being able to start using it rather than waiting for a perfect app. However, this mentality should never be used on an app that the final customers are going to see, or if there are immense governance standards to comply with.
Sometimes hasty progress is just not possible, and when a project cannot be accomplished rapidly, split up its parts to appease an impatient audience. This way, they can slowly get the pieces of the puzzle a little at a time. If splitting up the project is not possible, simply learn to say “no” to the users. Take a moment to explain in simple terms why it is too complex to quicken its development.
It is more cost-effective and time-effective to test applications off the premises. A cloud provider can deploy the application development required, and the internal staff does not need to be bothered with it. Collaboration between cross-functional IT and an end-user team builds a stronger relationship and opens the line of communication, in addition to creating a higher potential for success.
When working with rapid application development, it is important to have the end-users alongside throughout the entire process. Any corner-cutting in the development of the app should be agreed upon by all parties. If the app is going to be developed rapidly, it should be first agreed upon with the end user that no major enhancements will be made by the launch date.
Rapid development is sometimes best kept in-house. This allows for IT to focus its attention directly on the work and not worry about any third-party involvement, if the parties in question are particularly sketchy. When under a time crunch, it is best to stick with what is already known. Avoid making a deadline that does not take into account the possibility of mistakes.
You can read the original article here: http://www.techrepublic.com/blog/10-things/10-ways-to-implement-fast-it-without-risking-failure/