The Arc-E-Tect's Prediction on Products and Projects

Why Products? Because products are supposed to outlive the projects that created them and 2017 we finally see that value creation is the sole reason why we do IT.
The main difference is that we'll see IT as a product and we'll be delivering products to users. We might be doing this in projects, but organisations will switch from a project oriented organisation towards product oriented organisations. The main impact will be organisational. Of course, but organisations are (becoming) ready for this. For one teams will become responsible not only for the creation of solutions in a project, but also for operating those solutions. There won’t be a developer and an operator in those teams, but people doing both. These teams will be responsible for the products they create. That’s a responsibility towards the user. Secondly the these product oriented teams will be considered business teams as they are creating business value with the products that are developed. Accountability for the success of the products in a business concern. Mind that in 2015 we already started to consider security and compliance to be business concerns and not an IT concern. In 2017 we’ll start to see the success of our products and not only its security, to be a business concern as well. The gap between IT and business will be benign.
Thanks once again for reading my blog. Please don't be reluctant to Tweet about it, put a link on Facebook or recommend this blog to your network on LinkedIn. Heck, send the link to my blog to all your Whatsapp friends and everybody in your contactlist. But if you really want to show your appreciation, drop a comment with your opinion on the topic, your experiences or anything else that is relevant.
Arc-E-Tect
Products in, Projects out
It shouldn't surprise you, but I'm not a big proponent of projects and instead love to see it when organisations switch to a product focused approach. But in 2017 it will turn out that I'm not the only one.The main difference is that we'll see IT as a product and we'll be delivering products to users. We might be doing this in projects, but organisations will switch from a project oriented organisation towards product oriented organisations. The main impact will be organisational. Of course, but organisations are (becoming) ready for this. For one teams will become responsible not only for the creation of solutions in a project, but also for operating those solutions. There won’t be a developer and an operator in those teams, but people doing both. These teams will be responsible for the products they create. That’s a responsibility towards the user. Secondly the these product oriented teams will be considered business teams as they are creating business value with the products that are developed. Accountability for the success of the products in a business concern. Mind that in 2015 we already started to consider security and compliance to be business concerns and not an IT concern. In 2017 we’ll start to see the success of our products and not only its security, to be a business concern as well. The gap between IT and business will be benign.
I can be short about projects, they won’t disappear in 2017. There will be more than ever, but their impact on the business will be less interesting from this year forward. As the overhead of doing projects is increasing almost exponentially because of all kinds of reporting requirements, there is a necessity to increase the size of projects in order to make it worth our while to run a project. This is spiraling out of control and to put a hold on it, we’ll see organizations drop the heavy duty control mechanisms like Prince2 and adopt extremely lightweight governance structures in place, which in turn requires tiny releases, often. And this puts it all in place to develop products feature by feature. Hence… Products in, Projects out. Which automatically means that the Product Owner will be the hero of 2017 and the Project Manager is no longer there to save the day, something that can be read about in another post.
Thanks once again for reading my blog. Please don't be reluctant to Tweet about it, put a link on Facebook or recommend this blog to your network on LinkedIn. Heck, send the link to my blog to all your Whatsapp friends and everybody in your contactlist. But if you really want to show your appreciation, drop a comment with your opinion on the topic, your experiences or anything else that is relevant.
Arc-E-Tect
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.