The problem is that traditional estimating, timelines, team dynamics, etc., just don’t fit as well when developing mobile apps. Yes, you still have to plan, analyze, design, and build. But it needs to be done faster, and there’s an expectation of cheaper development (maybe something to do with the small physical footprint of a phone vs., say, a big enterprise server or mainframe). I dunno. I do know that teams are smaller, users are more closely involved, IT people play more than one role (PM/BA, developer/designer/tester, etc.), and it’s necessary to move the project along quickly and efficiently. Mobile moves fast, and expectations for IT people are becoming more demanding.

While we haven’t figured it all out yet, we have seen the light and are now using small diversified teams that marry the right amount of planning, technology, and artistic talent to get things done quickly and demonstrate progress. Some people would say this is just Agile development in action, but it’s more than that; it’s a new shift on time and expectation. You have to be fast to be first, and being first with your mobile app is key to many customers. IT will need to relearn and retool more quickly to meet these demands. We at Fusion have seen and met this challenge.

SOUND OFF:  What challenges has your IT team experienced with creating mobile apps?