IBMImpact

There is a difference between what role IT should play in #IoT vs. what they will play.

#IoT is a rapidly accelerating area for enterprise mobility. Connected Cars, sensors, wearable devices.

All of that requires massively parallel capabilities for scaling transactions and analyzing data. 5 petabytes of data are generated on mobile devices daily.

The Q s/b: How to get IT to play a leading role in #IoT within the #cloud & #mobile architecture.

So, clearly transformational but a lot of new issues around privacy, security, and data ownership

@edbrill wearables are a big consumer trend and sensors etc power businesses.. so interesting to see how the data layer handles

@tcrawford I see IT setting data policies to capture the data and use it as an asset; then enable developers to program with is "play with the data"

Architecture, data strategy, workflow, security...it's complicated w/ lots of headwinds.#IoT

@edbrill we saw a lot about wearables trending last month at sxsw. A lot of interesting technology and innovation!

I say the mantra is Built Grow & Monetize the developer environment and underlying infrastructure

One of the challenges is being able to build and deploy solutions for all sorts of devices, operating systems, form factors. IBM's MobileFirst Platform takes care of these complexities in build/test/manage/deploy phases.

How ready are the larger organizations? More Push or Pull?

A study we did in Q4 2013 found that less than half of all organizations have a well-defined mobile strategy.

@JeffFrick do you mean how projects get initiated or deployed or both

@edbrill So what are the key attributes of a successful mobile solution experience?

@edbrill -> Is "Well defined strategy?" counter to the the current agile thinking, get started , adjust. How does that fly in large organizations? Where are you seeing early adoption, success?

I talk to IT practitioners all the time who say they have a love/hate w/mobile - they are challenged to accommodate users, secure & integrate mobile & at the same time they're mobile users too!

To @JeffFrick I think there's a way to be agile and have a strategy…mobile devops can help with fast cycle time and iterations of solutions to start with something simple/responsive and move fast. But in the second wave a strategy is important to guide.

@dvellante -> those pesky users, and hyperscale companies setting app behavior expectations

I heard someone this week suggest that BYOD is leading to the demise of IT. MyPOV: Misplaced perspective.

Consumerization of IT significantly impacts the way firms develop mobile device security plans. @maas360 is taking a leading role in helping clients with this.

I'd separate the two. We have thousands of customers for our #MaaS360 enterprise mobile management solution. BYOD is here to stay in certain industries and markets.

still a lot of talk and others that have moved in that direction are using VDI to accommodate users

Mobile First is a strategy for organizations that recognizes that mobile today is primary, and to adopt transformational mobile enterprise solutions to take advantage of the second wave of mobile.

Having less that 5 function approach for an App. Solving only one purpose and doing that Good within the small real-estate.

if dev right for mobile it will work across multiple channels. It's mobile first, not mobile only

@edd

@edd what is that second wave of mobile

MobileFirst developers have the freedom to use cloud and/or on-prem resources, and develop native or hybrid mobile apps.

@CrowdDr great point there is a distinction between web vs mobile for sure; as a developer what are the key issues

The next wave of mobile apps will integrate wearables - watches, glasses, belt buckles and shoelaces.

Web apps allow developers to target more devices, but native mobile apps can take advantage of the latest cool device capabilities - so there is a trade-off between dev productivity and app uniqueness.

I would add is it different by vertical mkt or solution?

imo it's energized the role of the CIO. It shifts the focus from keeping the lights on to adding new value that is much more easily funded...with a common (mobile first!) architecture. Great opportunity for CIOs to innovate

According to a recent report, IT spending is slated to increase 3.2% in 2014 driven by #mobile & #cloud.

@dvellante I think that driving top line revenue is a great opportunity for CxO to flex the value muscles

I don't think it's different in verticals. The key for the CIO is to define a strategy and governance as they do in other areas. For mobile, though, it needs to be able to operate with speed and flexibility like never before.

The shift from traditional #CIO to transformational #CIO has sparked new opportunity and excitement around IT.

@tcrawford here is the link for IT spending stats you shared http://www.gartner.com/newsroom/id/2698017

It is clear that IT & business perspective on the mobility journey is shaped by their context, business objectives, requirements imposed by the size of their organization. What is the best way to select a starting point & to ‘connect the dots’ from there?

A key metric to indicate whether a moile app is successful is continued usage - more than 80% of apps on most smartphones get used once after downloading.

ROI is a key metric. Worklight customers have generated up to 363% ROI on mobile app projects.

It is important to iteratively improve mobile apps to encourage repeat usage.

Moble devs have to be #agile, mobile apps are updated on a monthly or even weekly basis. quick release cycles is key to successful mobile apps

I think the tools we have, like IBM Worklight make it easier to be more agile with mobile development.

New mobile cloud services like IBM Bluemix also help with agile development

@rfavali great point this is key distinction; liked the comment mobile first isn't mobile only

Sure - effective mobile development is inherently agile, since it uses rapid iterations in response to customer feedback --> not doing it this way would be fragile rather than agile.

They have different approaches. In cloud, like IBM's Bluemix project, an individual developer - say in line of business like a power user - can assemble an app from components and deploy on the spot.

both environments are abstracted away but will coexist bc the data and other systems will be critical in rolling out interoperable data and apps in the enterprise

On-premises, like IBM's Worklight platform, provides the full lifecycle of capabilities for building/managing/deploying multiple applications, especially useful in business-to-employee scenarios but also effective in B2B/B2C

organizations need holistic business plan for moble supported by c-level, LoB and IT. Determine goals and then best approach to implement cloud or on Prem. IBM can help with both