Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
A complete cloud platform for an app or your entire digital business
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
An enterprise mobility initiative can tempt organizations to silo mobile development teams. Here’s some considerations that may help you avoid that mobility trap.
Silos exist in every business. They are an unintended consequence of management strategies. Organizations tend to become over-focused on the objectives asked of them and gradually tend to ignore or become less coordinated with other organizations within the business. The net effect of this silo development can be increased costs, decreased agility and growing inefficiency.
IT often struggles to overcome the effects of silos, too. For example, development groups and IT operations frequently “speak different languages” that can cause frustration. IT ops is brought in late in the game, while dev groups tend to throw the finished application “over the wall” to IT ops without fully considering how it will be used or maintained.
At that point, IT ops is stuck taking the app, deploying it in production, monitoring the application and resourcing the help desk function when the end user has a problem. The DevOps approach aims to bridge this divide.
A mobile application development silo can exacerbate the divide between Development and IT Operations.
Given the problems with silos, when stepping up mobility efforts it’s probably worthwhile trying to avoid a mobile app dev silo. If you choose to have silo a mobile development team for organizational reasons, make sure that you have the process and people in place that can manage the abstraction level appropriately.
Here are some points to consider:
If you choose to keep your mobile team separate, take some advice from Forrester. The firm says that some organizations silo intentionally, “to keep a fresh approach, complete major redesigns in under a year, and then gradually socialize mobile.” Other organizations choose to keep mobile development separate at the outset, and then work to integrate development efforts after they have socialized mobile. Whichever path you choose, think about the integration points that are necessary to eliminate barriers to your success.
For more on avoiding the mobility trap, download my latest whitepaper, “9 Essentials to Create Amazing Applications Faster.”
We’d love to help you get started with a Platform as a Service (PaaS) environment that enables DevOps across your IT organization. Contact us now and we’ll get back to you right away.
Mark Troester is the Vice President of Strategy at Progress. He guides the strategic go-to-market efforts for the Progress cognitive-first strategy. Mark has extensive experience in bringing application development and big data products to market. Previously, he led product marketing efforts at Sonatype, SAS and Progress DataDirect. Before these positions, Mark worked as a developer and developer manager for start-ups and enterprises alike. You can find him on LinkedIn or @mtroester on Twitter.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.