Mobile QA Zone

A Mobile Application Testing Community

Why Agile flavour in not suitable for embaded and mobile domian..

in my point of view hardware play an important role in embadded domain.hardware will decide which techonology is suitable because if we implement scrum in mobile domain hardware it will play as a stakeholder.it is possible to implement in web application and other desktop application.because of different reasion like memory and fast processing speed.application is very cricual when we are creating a client server application. i will give u a example of an application like one of the application i am doing application is remotelly acces the device on pc.with the help of this application CSR can able to acces the client device and do some amendment with the permission of user, user means customer who is having a higher end device like window mobile,blackberry,andriod device which have higer capability.
this application is totally depend on hard ware like web service ,connection procter,databse capabilities. so it is totally depend on hard ware capability and device capabilty.hard ware decide what we can do or possibilities.so stake holder has to wait and ask to the scrum member or team to know the flexbilities.so always dependent to the team what they suggest and the team will also deside the time frame and added functionality. so in this situation every ting is depend on the team and scrum master.stake holder will play like a pupet and decide after team will decide what he will do next.

Extreme Programming emphasizes teamwork. Managers, customers, and developers are all equal partners in a collaborative team. Extreme Programming implements a simple, yet effective environment enabling teams to become highly productive. The team self-organizes around the problem to solve it as efficiently as possible.stake holder is a part of team.

why agile flavour is not suitable because:
With agile iterations only a few weeks long, do agile teams really expect to modify hardware that frequently?
In embedded systems development hardware, software and mechanics are built concurrently.
We had a team doing agile. To them that included not doing any documentation. We need documentation once we go into maintenance. Is doing documentation allowed in Agile?
Hardware is often not ready until late in the product cycle, how can testing be continuous from the beginning without hardware.
tell me your comment if i am wrong......

Views: 91

Comment

You need to be a member of Mobile QA Zone to add comments!

Join Mobile QA Zone

Comment by Ruma Dak on October 9, 2012 at 10:26am

I don't completely agree with you Sanjay!

First thing, there is a different flavour of AGILE followed by every company.

I ahve worked on an enbedded project for 2 years and we followed AGILE. Currently, I am working on Web and Mobile application and it is also Agile.

And Agile is not about no documentation. You need to be flexible and cope with your time constraints in the most effective way.

Comment by jyoti suden on October 8, 2012 at 5:24pm

very informative.....................

Comment by Divya on September 20, 2011 at 2:53pm

 

Arun, Thanks for posting :), So Xp is the type of  Agile model, but am not getting How xp differ from Agile. Can you explain why XP is better than Agile? 

Comment by Arun Francis on September 20, 2011 at 1:59pm

Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development,it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted.Other elements of extreme programming include: programming in pairs or doing extensive code review, unit testing of all code, avoiding programming of features until they are actually needed, a flat management structure, simplicity and clarity in code, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.The methodology takes its name from the idea that the beneficial elements of traditional software engineering practices are taken to "extreme" levels, on the theory that if some is good, more is better. Other words its a combination of CMMI and Six Sigma.............. :) 

Comment by Divya on September 20, 2011 at 10:36am

 

What is xp model?

Comment by Arun Francis on September 19, 2011 at 1:53pm
No confusions Sanjay :)
Comment by sanjay kumar on September 16, 2011 at 7:04pm
u guys are confuse because agile and xp are somewhat common
there is slighly different.basically we are using incremental,xp or some times we are using prototype model in mobile domain.
Comment by sanjay kumar on September 16, 2011 at 7:02pm
some times i am agree with u arun but most of time we are using xp,there is some different between agile and xp,in mobile industries.very soon i will write one blog in xp then u can easly differenciate..thaks for your comment it really appricate me to write a good blogs..
Comment by Divya on September 16, 2011 at 5:55pm

 

@ Sanjay : I am completely agree with Arun's comments 

Comment by Arun Francis on September 16, 2011 at 5:18pm

Hi Sanjay, Todays software field s sailing n Agile process including mobile domain also.Y am saying dis 1 bcoz all mobile apps r not long term 1s.Maximum they r short 1s , day-day client(stakeholder) will change the req after viewing apps including designs and functionality. So it bests fits agile process 1ly.

Thanks :) 

© 2014   Created by Anurag Khode.

Badges  |  Report an Issue  |  Terms of Service

Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.