Architecture Of Agile
Architecture of agile is the representation of process which is help to give desired output/application. Agile architecture means how enterprise architects, system architects and software architects apply architectural practice in agile software development.It is interaction between team member.
It is process of beginning of the application and helps to developer ,tester, and other team member to analyses the product requirement and expectation of client. It is blueprint of starting of product( means development) and end of product( means Deployment) of product.
Stake Holder:-
Stake holder is top most contain of body of the company. Also known as client or customer. At any phase of development, testing and also production time they can request for change.
Project Owner:-
Project owner is nothing but the business analyst .Project owner is gathered the information from stake holder. It is team member of sprint planning meeting . project backlog is created by project owner.
Project Backlog:-
Project Backlog are total requirement of whole project. It includes requirements of all modules. A project backlog prioritized list of deliverables that should be implemented as part of a project development .
Different Types Of Agile Ceremonies [Meetings]
Estimation:-
It is nothing but a start date and end date of the project
Estimation is also called sprint planning meeting. Scrum master and product owner are host that meeting each team member should present in that meeting.
Main purpose for this meeting is which functionality we are going to take in next sprint, That functionality are discussed in meeting or we can goodly say that sorting of user stories.
That user stories explained by product owner in his way means what we need to do? What is expectation?
After that scrum master will allocate user stories to us according to resources at that time he will check three factors like Knowledge, efforts, complexity.
Sprint Backlog:-
Sprint backlog created by project owner. It contain user stories. It contain detail requirement which are required for module development.
User Stories:-
It contains the set of use cases/requirement which is related to the same module.User stories are nothing but specific requirement of particular sprint which contain Description and Acceptance Criteria.User stories are decided in the estimation phase It is functional requirement that is specific Requirement of particular sprint. User Story focuses on what the user needs instead of what the system should deliver.
Test Cases:-
Use cases define functionality of specific requirement. Use case prepared by BA (Business analyst). Test scenario mapped with Use cases.
Tester designed Test cases . Test cases mapped with user stories. Tester will identify the test scenario
For every US, Identify the test scenario. On the basis of test scenario tester write test cases. Form test scenario, tester will prepared test cases.
What is user story?
User stories are nothing but specific requirement of particular sprint which contain Description and Acceptance Criteria.User stories are decided in the estimation phase It is functional requirement that is specific Requirement of particular sprint. User Story focuses on what the user needs instead of what the system should deliver.
What is sprint backlog and project backlog?
| Sprint Backlog | Project Backlog |
|
|
|
|
|
|
|
|