Talk:2080 Software Development

From 2080 Development community.

The advantages of 2080 for your business

For most companies I work with, large software projects are a real pain. While most large companies have increasingly more professional IT organizations, spend enoromous budgets on training and involve the guidance from the typical IT consultants it does not seem to make any difference for your software project. New It platforms continue to suffer from - Major delays in the delivery of the platform (e.g. 6 months up to 1 year is considered as 'normal') - A big gap between what was expected as a improvement result for the business versus what can be realized (e.g., efficiency improvements) - Missed opportunity to re-think the business value of the platform. I noticed several 'new platforms' who did not add any new advantave for the business but were merely "IT upgrades' - Sceptical end-users and clients ("we need to see it first")

While the examples mentioned above indicate that today software development projects are typically a painful experience, there is also an alternative. The alternative can be labeled under 2080, or you can call it common sense, but it is an approach that we all use on a daily basis. It starts with breaking down major deliverables in milestones that we can understand and see how to reach them. Is this not the same what you would do for any well-managed project?

Developing a proven prototype basis has 3 major advantages: 1. You can experience and see what is most valuable to add next to your application (so the end-application will look differently from what you have originally thought). This allows a cross-fertilization of business and IT that otherwise would never happen. It is exactly the reaction of your teams to the delivery of the prototype that creates most value. "if we would have this button there and that report there, that would save us a lot of time". "Have you thought of doing this completely different?". Typically people only give added-value input when they can react to the screens of the software and using a prototype allows to do so.

2. You can already start building on the end-user acceptance. Buy using a prototype you can collect input and create buy-in from the organization. Not only will your end-user acceptance increase, also your budgeting will work easier. Using this early version allows to better align business needs to delivery of the project (no expactance-delivery gap)

3. In several case you can already extract value from this first version for the business. Showing early working functionality builds credibility and allows the business to align their plans to the release of the software. (e.g;, now the business typically waits 6 months after the final release to startusing the application)