Managing a mobile project always has its own set of unique challenges just like all the other projects that are meant to be successful in the IT industry. Mobile technology being in vogue and being everywhere and for everybody, the challenges become more complex and need a special treatment. There are instances when all that client have is an IDEA (rather a MILLION “$$$$” idea). And with huge diversity in the domains such as Mobile OS, user age group and (super*) human expectation/imagination of the human beings, the work becomes even more challenging.
I have been working in Mobility for years now and all we needed to do was answer following 4 questions during the execution:
- Will you be able to address the current business requirement?
- Will you be able to provide a stable and best quality product?
- Will you be able to make the solution scalable to support ever evolving requirement?
- And most important will you able to survive evolving mobility scene?
All the stakeholders should be able to achieve Visibility, Adaptability to both latest market trends with the aim of adding Business value with least Risk.
The only modus operandi that could come out was to make sure we as a team are able to achieve following 3 Cs,
- Coordination
- Communication
- Control
Regular coordination and communication helps to build strong relationships within the team which in turn forms a strong trust factor- by and large the most important ingredient for a successful team. It is highly important for the team to understand the same project language.
All these factors help achieve a common goal known to everybody involved and the one that everybody is thriving to achieve. And all these efforts along with regular check-points will make sure we complete control over the assignments.
We need a flexible, holistic product development strategy where a development team works as a unit to reach a common goal. And the answer is SCRUM. The following table will summarize it:
