Agile Methodology Summary

1180 Words5 Pages

Summary on Agile Methodology
I want to write a brief summary on Agile methodology.Before going to explain what is Agile,I want to explain what are the models we follow in Software development process.In any projects the main aim is to satisfy the customer requirements in form of Project deliverables,change in requirements.In large companies we need to follow some standerd process to get the best outcome.
In projects we have phases like Requirement,design,development,testing,maintainance.In case of traditional waterfall model will complete one entire phase before moving to the next phase.Will go with testing at end of project.in this development phase will take lot of time.Once the requirement done …show more content…

Agile welcomes change by allowing the Product Owner to continually prioritize and re-order requirements for subsequent Iteration. Agile Software Development is an umbrella term for several iterative and incremental software development methodologies. The most popular agile methodologies include Extreme Programming (XP), Scrum).In agile methodology every day will assign one task to the resource and they have to doucumnt the status at the end of the day.It will mainly used in the projects where the technology and requirement will change …show more content…

Only if the scope expands to a point where it impacts the duration or the number of resources committed to the project will a formal Change Request be necessary. In most cases, the Product Owner is so closely involved, changes of this magnitude don’t occur. Instead, new scope is prioritized first for the subsequent release.
In any project there will be dependencies whether they are external or internal ,in agile will follow some steps to manager dependencies. During Iteration 0, the core team should analyze the User Stories in the Product Backlog to identify dependencies.The Project Manager and Scrum Master should communicate dependencies to external and internal teams and obtain buy in and commitment from the teams to participate and deliver, as required.During the Point Estimation and Release Planning process, scope the features for the Iterations in such a way that the dependencies and commitments from various groups are

Open Document