Anadi Mishra.
Originally posted by Anadi Mishra:
So with all rosy I now went to the next project. a huge one i must say; 6 teams 50+ developers in teams of 10-15 each developing each of the sub systems in this titanic thing I am talking about.
[...]
1) Is the combo suitable for small sized teams (or projects) only?
Originally posted by Anadi Mishra:
2) Some one gave an interesting thought that one never really has time for performance / load etc and the like as it will be more harmful if the product owner does not see the functionality at the end of the sprint rather than giving a sub performing system but yes all functionality delivered.
Originally posted by Anadi Mishra:
3) Is it that for large projects using which are some where in the core based on a product, if using Agile etc it is better to just develop on top of that product than tweaking/changing it around to suite your needs better?
Originally posted by Anadi Mishra:
4) Is it viable to have an independent Integration Team which can point out "Hey this is gonna hurt badly later"
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
To some degree that helped make lives easier during a project but didn't solve the actual problem - how to build software with a large group of people -
Anadi Mishra.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Anadi Mishra:
Cant there be a scrum of scrums thing to tackle such problems? I had that opinion but you cant win all arguments in life
Keep Smiling Always — My life is smoother when running silent. -paul
[FAQs] [Certification Guides] [The Linux Documentation Project]
Keep Smiling Always — My life is smoother when running silent. -paul
[FAQs] [Certification Guides] [The Linux Documentation Project]
How do you have sprint deliverables, one per team or one for the whole project?
Anadi Mishra.
I am not into project management anywhere but yes from my personal perspective it is not just agile to be blamed off.
Anadi Mishra.
Amr Elssamadisy<br /><a href="http://www.amazon.com/Agile-Adoption-Patterns-Roadmap-Organizational/dp/0321514521/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1220909336&sr=8-1" target="_blank" rel="nofollow">Agile Adoption Patterns</a>
So, for example, one of the differences between a small team and a large team is the overhead involved in communication. Therefore communication practices will generally take precedence in a large team to mitigate this difficulty. More attention will need to be paid to information radiators, keeping team meetings short, and visibility. As noted in some of the comments above, continuous integration becomes crucial, etc...
Anadi Mishra.
Amr Elssamadisy<br /><a href="http://www.amazon.com/Agile-Adoption-Patterns-Roadmap-Organizational/dp/0321514521/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1220909336&sr=8-1" target="_blank" rel="nofollow">Agile Adoption Patterns</a>