1. The best methodology for software development process (POV)
Hani Gamal
2. Agilility Agility is about being smart,active, fast, fat
free, how youget things done! It is not about using the
agilemethodology
3. Process RequirementsDivide and conquer strategyreduce
risks.
4. Process Requirements A working software thatfulfills the
business needs is the aim but as example documentation is part of
the process too!
5. Process Requirements Accurate business, systemand user
scenarios analysis.Need better prospecting?
6. Process RequirementsFast development meets deadlines is
essential?
7. Process Requirements Deliver highest quality at a relatively
low cost.
8. Process RequirementsDetailed time tracking of the whole
process.
9. Process RequirementsSmooth production and easy
implementation.
10. Point of view Applying a particular standard methodology
iswrong by all means; The bigger mistake is not tochoose one!
Accuracy and clearance of requirements areessential and should be
part of the cycle. Clients should be involved in the process but
not indecisions. Quick responses to changes is essential but not
inexpensive cost and not without a plan. Time estimation is not a
sacred rule but perfectionis possible too! A week is very good unit
of measure but a day is notbad for measurment too! Team interaction
is the most important but thatdoesnt mean processes & tools are
not or less! Self-organized team is good but a responsibleproject
coordinator is better. If no PM software meets your requirements
dontcreate a new one unless youre a softwaredevelopment house.