2.3.3
Agile Methodology
Agile Methodology
Agile Methodology
When working in software development organisations follow software development systems to ensure the project is a success. Agile methodology is one such system.
Agile methodology
Agile methodology
- Agile methodology has a series of stages like the waterfall lifecycle.
- Some of the stages are repeated to allow for people to change their requirements and develop a product over several iterations, called sprints.
User requirements
User requirements
- The agile system starts with user requirements, with a focus on splitting up the project into user stories.
- User stories are descriptions of the different ways the system will be used, what it will look like and what they expect it to do.
Sprint
Sprint
- A development sprint is a short time-frame during which a specific user story is completed.
- A sprint planning meeting is held to prioritize and categorise these user stories and set up the work for the development sprint.
- This product is a fully working “deliverable” that the client or market can use instantly.
Iteration
Iteration
- The deliverable is given to the client.
- The product is evaluated and this information is fed back into the next sprint planning meeting.
- The sprint planning meeting and the sprint are repeated multiple times until the full scope of the project is agreed as finished.
Merits & Drawbacks of the Agile Methodology
Merits & Drawbacks of the Agile Methodology
Software development methodologies are suitable in different situations and all of them have positive and negatives.
Merits of agile
Merits of agile
- With an agile methodology, the client can take a product to market more quickly.
- Clients can receive incremental updates for the product.
- The final product has absolute certainty that it is what the client wanted as they are constantly involved with its development over each iteration.
Drawbacks of agile
Drawbacks of agile
- Agile offers less predictability compared to waterfall for timings and costings as the process constantly repeats.
- Agile methodology requires higher time input from the client as they are constantly required for feedback and consultation at all stages of the development process.
- Agile methodology can easily go off track and a project can last well beyond the initial idea, meaning high costs and high time input.
Usage
Usage
- Agile is best suited to projects where the client has a good idea of what they want, but also has a lot of time they can invest into controlling the project and feeding back on it.
1Components of a Computer
1.1Structure & Function of the Processor
1.2Types of Processors
2Software & Software Development
2.1Systems Software
2.2Applications Generation
2.3Software Development
3Exchanging Data
3.1Compression, Encryption & Hashing
3.3Networks
4Data Types, Data Structures & Algorithms
4.1Data Types
5Legal, Moral, Cultural & Ethical Issues
5.1Computing Related Legislation
6Elements of Computational Thinking
6.1Thinking Abstractly
6.2Thinking Procedurally
6.3Thinking Logically
7Problem Solving & Programming
7.1Programming Techniques
7.2Programming Construction
Jump to other topics
1Components of a Computer
1.1Structure & Function of the Processor
1.2Types of Processors
2Software & Software Development
2.1Systems Software
2.2Applications Generation
2.3Software Development
3Exchanging Data
3.1Compression, Encryption & Hashing
3.3Networks
4Data Types, Data Structures & Algorithms
4.1Data Types
5Legal, Moral, Cultural & Ethical Issues
5.1Computing Related Legislation
6Elements of Computational Thinking
6.1Thinking Abstractly
6.2Thinking Procedurally
6.3Thinking Logically
7Problem Solving & Programming
7.1Programming Techniques
7.2Programming Construction
Unlock your full potential with GoStudent tutoring
Affordable 1:1 tutoring from the comfort of your home
Tutors are matched to your specific learning needs
30+ school subjects covered