Defining the best methodology for software development process

1. The best methodology for software
development process (POV)
Hani Gamal

2. Agilility
Agility is about being smart,
active, fast, fat free, how you
get things done!
It is not about using “the” agile
methodology

3. Process Requirements
Divide and conquer strategy
reduce risks.

4. Process Requirements
A working software that
fulfills the business needs is
the aim but as example
“documentation” is part of
the process too!

5. Process Requirements
Accurate business, system
and user scenarios analysis.
Need better prospecting?

6. Process Requirements
Fast development meets
deadlines is essential?

7. Process Requirements
Deliver highest quality at a
relatively low cost.

8. Process Requirements
Detailed time tracking of the
whole process.

9. Process Requirements
Smooth production and easy
implementation.

10. Point of view
• Applying a particular standard methodology is
wrong by all means; The bigger mistake is not to
choose one!
• Accuracy and clearance of requirements are
essential and should be part of the cycle.
• Clients should be involved in the process but not in
decisions.
• Quick responses to changes is essential but not in
expensive cost and not without a plan.
• Time estimation is not a sacred rule but perfection
is possible too!
• A week is very good unit of measure but a day is not
bad for measurment too!
• Team interaction is the most important but that
doesn't mean processes & tools are not or less!
• Self-organized team is good but a responsible
project coordinator is better.
• If no PM software meets your requirements don't
create a new one unless you're a software
development house.