3 ms·
There are no need for formal methodologies. A person with no technical expertise should not be but on a position managing technical teams. That requirement divi
by baybal2 9y ago
There are no need for formal methodologies. A person with no technical expertise should not be but on a position managing technical teams. That requirement divides the industry on "tech companies" and everybody else.
The example of a tech company with gigantic dev teams and very little number of MBA doctrinaires involved in development process is Intel.
Companies with external development clients that practice "we will agree on any methodology you want for right amount of money, but we would not let you anywhere close to our developers (who will be doing their own thing anyways)" are Tatas, Wipros, Luxofts and others. Their biggest asset is their skill at managing the client.
- walshemj 9y agoAh and how would say produce a management system for a core part of a country's core data network (I was a team member developing a management system for the UK's SMDS network) with out a process? - In this case we used a hybrid waterfall /RAD system 12 weeks to develop the fist release
- baybal2 9y agoThe very very few cases where anything called a methodology works is when you deal with a repeating tasks: making a customized versions of standard tools, or what people call copy&paste development. SAP does it very well. Charges people 7 digits for "customized solution" that in reality is not customized beyond 20 lines of code from what the company sells to every sixth or seventh client. The goal there would be to not to dive too deep into the task that is already solved in a way that "works well enough," and for what the client is already ready to pay money for.
- walshemj 9y agoNot everyone always works on me to crud applications leaving aside SAP and other "miracle" tools :-)
- Clubber 9y agoI think the key word is "formal," to me, meaning a strict process to be used at all times in all situations. Like anything in development, it makes better sense to use whatever process works best for whatever team is implementing whatever solution is needed.