2. Conception of developing a mobile app for Rational Quality Manager (RQM)
AjayChebbi devWorks 270004DG8B Visits (1810)
A little re-wind is in order. It all started with a intern project and a craving for doing something cool. I work in a team that develops the Rati
2 years ago a intern started developing a mobile app for RQM. The approach we took was "hot shot execs use iPads, and they are always in meetings, and they think mobile apps are cool." So lets develop a mobile app that will allow them to view Quality dashboards etc. We thought it would be cool to give the test leads the ability to view test scripts and approve them etc. This is when Worklight was not yet acquired by IBM This effort turned out to be a good technology understanding project and got the intern her degree.. The use case did not get much traction - because the obvious thing for some one with the fancy iPad to do is open the browser and connect to the RQM server and get the work done! We also discovered that execs live and breathe power point... they even have people to make power point OMG! So there was no point to the power of getting them a app. (Just so that readers are clear that I am not making a career limiting move - these are not "my"execs I am taking about.. not in my food chain AT ALL)
Like Edison would have said - one more way to not make a bulb!
I took a step back.. and started asking around what is a problem to solve? What is it that people will "pay money for". "Pay money for" is a metaphor I am using to gauge the pain point..you need to ask that question even if you are developing something that you want to give away for free... ever heard of the phrase "I don't want it even if you give it to me for free!"
I spoke to my good friend the product manager. What are the pains customers are facing that I can solve with a stand alone program (I purposefully kept it abstract). he said if you can develop a application that will let our systems customers run manual tests offline that would be great.. and I will take it for free. (that's just a phrase for we cannot dedicate development resources because of other development pressures (we developers call them bugs ) .. All right - lets try to solve that problem!