Agile Methodolgy

We go for Agile mode while we face below scenario

-> unclear Requirements
-> Frequent requirement changes
-> want to release project Quickly output for partial requirements.
-> While implement new Tecnology in organization
-> New type of project implement in organization.


We dont have clear documents while implement new tchnology or new type of project implementation. so we can follow  below steps,

If raise Problems -> Take Discussion -> Find Solution -> Implementation


Drawback

Sometimes the Agile Model may deviate from objective or Planning of the project.



Agile Model

1) Requirements

2) Identify the scope and list out the Module from the requirements

3) Take the one module from list of module then do follow process
    i)  Planning
    ii) design
    iii)Implementation
    iv) Testing
    v)  iCAT / eCAT
    Vi) If the client satisfied by the product then move to next step (4). Otherwise loop continued from step (i).

4) Take next module from list of module and loop continued from step (3).

5) If all the module get completed then finally the project moved into Maintanance.







Agile Scrum

Agile Scrum used to organize the Agile model.

The drawback of Agile model is we may deviate from objective or Planning of the project because lot of discussion made for find solution. so we follow below steps for overcome this problem

1) Assign perticular person for monitor the process if any deviation  from plan  for Agile process.

2) And maintained seperate document for keep track the process if find any deviation  from plan  for Agile process.

If the above two process implement in Agile model then its called Agile Scrum.


Sprint

Project is divided into sprints

1) One module divide into many functionalities

2) Then each and every functionality divided into many sprint. Those all sprits are do some tasks for according functionality.

3) we can keep track for those sprints for every one week or max 30 days. And monitor we may deviated from planning or not.

4) Then finally we release the sprint into production.


Product backlog - Maintain list what are functionality left and need to implement.

Sprint Burndown Chart - Maintain list what are sprint left and need to implement.

Release Burndown Chart - Maintain list what are release left and need to implement.




who involve in the Agile Scrum

-> Product Master - He is client and define the requirements. From that we can identify the objective and planning.

-> Scrum Master-> He is intermediate from Product master and Team member. If team member have any doubts then scrum master clear those doubts after discuss with Product master if needed.

-> Team Member -> He is software engineer to implement the project.



Buisness alayst always should be present intermediate between Technical people and product master. becasue technical people speaks technically its not understand by product master.

Then finally the product master clear all doubts when its asked by technical people. so its better to analysis.