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......