PM Methodologies for MobileDevelopment (iOS/Android)?

Question

Project management

Interested precisely not with tz. the author of the idea / code, and from the point of view of understanding what processes the design flow consists of, for a clear definition of resources: terms, cost of stages, man-hours.
Specialization in MobDev: utilities (not games).
Role: customer + PM (management and coordination of contractors' work)
I would like to find:
- a set of development stages;
— a set of task categories;
- template/example.
In what I see the specifics for MobDev and what examples I would ideally like to find:
- interaction with designers (ordering several design options);
- stage of promotion (beginning and end, necessary resources);
— miscalculation of risks (terms / cost).

Answer 1

Do you really hope that someone will tell you their successful business model of creating mobile applications "in and out"? :)
Reminds me of the story " I want to release a super application that will bring millions, I'm looking for a programmer, and let him come up with a chip himself, well, like instagramm ".
But in essence - this is achieved by experience (both practical and theoretical) and 90% depends on the team and the PM itself. And this application will be mobile and logging is not so important.

Answer 2

For starters, read the methodology. I recommend RUP 6 (namely the 6th, not the 7th) in the teeth, and go ahead.
or OpenUP ( en.wikipedia.org/wiki/OpenUP, www.ibm.com/developerworks/en/library/kroll ).

I would like to find:
- a set of development stages;
— a set of task categories;
- template/example.

var.1 Buy Rational Method Composer (RMC).
There is a "process site" editor with examples and templates and a description of all procedures, documents, templates and everything else that you might need. The ideology of application in practice sounds like this: out of this disgrace - pull on what you need _on_this_ project - and get a description of the methodology and processes on your project. With document templates, instructions and descriptions of procedures.
There are both RUP and lightweight Agile-RUP, and even the classic "waterfall" with recommendations is described. Now it can be that for mobile applications, too, they saw it. I haven't watched for 2 years what's going on with them, but I hope IBM didn't mess up Rational's creation too much.
It costs "non-fucking money", but a month of a full-featured run of registration was free. IBM is more generous than ever. <_<
www.ibm.com/developerworks/downloads/r/rup
www.interface.ru/home.asp?artId=1524
www.itshop.ru/Dokumentirovanie-i-avtomatizatsiya-p...
var.2 Or feel his free eclipse prototype Eclipse Process Framwork. But there are not many templates. But there are a lot of their own, from the community. Including a handful of Agile processes, XP descriptions, and the like.
www.eclipse.org/epf
www.ibm.com/developerworks/rational/library/05/101...
PSQuestion of methodology, principles. It is they who allow you to build a set of everything-everything into something meaningful. Be afraid to draw in EMC what is your own without understanding at least the basics of RUP (I strongly recommend the 6th, because the 7th introduced the principles of business-oriented development, which technically are completely meaningless).
BUT! On the other hand, only EMC (and only EMC) can generate for you the most complete description of all RUP methods and procedures (including philosophy and principles). In general - make a website with a full description of RUP - you look and understand what. And you can start with wikipedia ( ru.wikipedia.org/wiki/Rational_Unified_Process ) or introductory articles on OpenUP ( ru.wikipedia.org/wiki/OpenUP, www.ibm.com/developerworks/ru/library/kroll ).
Do not be afraid of the first failures. It took me six months to start "thinking in iterations" and not try to prescribe everything at once. In order to master intelligible work using UseCases - a few more months.
PPS and forget about TK ;)
TK is a static artifact from a dark cascading-waterfall past.
Long live the iterative present, the discipline of "requirements management" and UseCases! (thrice "cheers"))))