PLM software lifecycle and social development roadmaps

PLM software lifecycle and social development roadmaps

social-product-development

My post few days about PLM software replacement cycle turned into discussion about the way companies are implementing and maintaining PLM software, upgrades, new versions and planning investments into infrastructure and enterprise software. My attention caught Technia on demand webinar – The future of SmarTeam. It is an example of long software development cycle, maintenance, support and transition of enterprise software. I can see it typical for PLM as well as for enterprise software category, in general.

At the same time, there are some changes in enterprise software domain these days. Software development is getting more social. Social networks and other social activities are helping to develop better communication with customers. It helps to make better alignment with customers and socialize around software rodmap and features. On the last point, I found few examples to share with you from Aras Corp, Autodesk and GrabCAD.

Aras Corp., developer of enterprise open software PLM software – Aras Innovator is maintaining transparency and visibility around customer requests and development roadmap. Navigate to the following link to see Aras roadmap. An interesting feature here is customer voting mechanism, which helps to prioritize development.

aras-social-roadmap

Another example is Autodesk community. Navigate your browser to PLM360 IDEASTATION link. It gives you an opportunity to socialize your ideas directly with development team, voting for ideas and discuss details.

plm-360-idea-station

GrabCAD blog earlier today – GrabCAD’s product development process: how new features come to life brings some insight about GrabCAD development process, communication and features’ validation process. Here is a key passage from the post:

After testing and making sure things work, we introduce new features to our most passionate power users to get the last round of validation and give the first taste of what’s coming. Even if you are super happy about the solution you came up with internally, always get feedback from smaller group of people outside of the company before unveiling it to the world. Fresh sets of eyes can see your product in a totally different way. This entire process is fast. An easier project might take a day or two while more important functionality might take a couple of weeks to build. If a project gets finished and published, there’s no time to waste. New improvements are waiting to be worked on and the cycle starts again.

I didn’t find a way to see GrabCAD Workbench online- maybe GrabCAD folks can comment on that below.

I’m sure this is not exhaustive list of PLM vendors and examples how they are socializing around requirements and development roadmap. So, if you have more examples, please bring them in comments or send me via email.

What is my conclusion? Enterprise software world is transforming. Social media and networking are bringing new methods of open communication with customers. I can see a significant influence of open source and web development communities. I can see this trend is growing in the future. To communicate first, discuss with customer and then develop will become a new software development norm in enterprise too. Just my thought..

Best, Oleg

photo credit: Rich B-S via photopin cc

Share

Share This Post

  • You are right, social development and feedback helps to improve software.
    beCPG is another example:
    – It’s open source so it is downloadable, users can try it
    – An online help
    – Forums allow to ask questions, give feedback
    – Community can post new requests and see requests posted by the community. Right now, we don’t publish our roadmap, internal and customer requirements. We just publish a release note. It would be an improvements to publish our roadmap.

    https://www.becpg.fr/redmine/projects/becpg-community/wiki

  • beyondplm

    Philippe, thanks for comments and sharing links! I agree- collaboration on requirements is an interesting opportunity. Basically, publishing roadmaps and voting is all about collaboration on requirements in a more efficient way.