W11 L3 - Intro to Agile Flashcards
1
Q
What is Agile
A
- A term used to describe a number of iterative development approaches that have developed over time
- Adhere to the Agile Manifesto
- Agile means nimble, responsive, or dexterous, and is used to describe the fact that agile methodologies, above all else, are intended to respond well to change—particularly changing requirements.
2
Q
List the main factors of the Agile Manifesto
A
- Individuals and interactions over processes and tools
- Main focus on stakeholders, what do they need.
- Would have more user stories than UCM or Activity
Diagrams - Working software over comprehensive documentation
- Go through iterations to get something functioning - Customer collaboration over contract negotiation
- Work in small teams to provide customer satisfaction - Responding to change over following a plan
- know you have to change and what t change along the way
3
Q
Describe Agile v Waterfall
A
Agile:
- Working software in every iteration
- Review and refine requirements regularly
Waterfall:
- Requirements are known
- Each stage signed off before the next stage starts
- Need extensive documentation as this is the main source of communication
- -> perfect approach if the requirements are fully understood and not complex
4
Q
What are the benefits of Agile
A
- Can show clients early on - this addresses the risk by minimise.
- Time - don’t have to wait until the end, the time to market is shortened with the iterations produces
- Cost - minimising the risk reduces the cost; depends on the project tho
- Quality is better - customers understanding their requirements better, more iterations to see
5
Q
What are implications of using Agile as a BA
A
- Techniques - Working with User stories
- Timing - all about iterations and working through each phase faster
- Activities and phases of SDLC
- Documentation - not as comprehensive
- Design and Development - understanding what is required and building it
- Small teams (~7) - waterfall can be big, but agile is smaller
- Agile Business Analyst
6
Q
What is a “sprint” in agile
A
- The goal is to have something working as soon as possible. MVP (Minimal Viable Product - want to make/deliver the process as fast as possible)
- Each sprint (for a shippable product/function) generally involves:
- requirements gathering - planning
- product design - design
- Coding
- testing
7
Q
What is Dual Track Development
A
Discovery and Delivery - these are two different processes
Discovery - want to maximise your learning velocity [speed at which you learn about a project]. Need to gather requirements and filter and analyse them
Delivery - want to maximise your delivery velocity - how to get what I understand out as fast as possible. Understanding the MVP and how you will push this out first, want this to be high quality.
8
Q
What are the 3 Discovery principles
A
- Encouraged to see the whole - consider other projects in the org, how will you project affect other e.g. problem or vision statement, DFD, Stakeholder analysis, Process modelling
- Think as the customer - having a good relationship and understand their needs e.g. User story, requirement workshop
- Analyse to determine what is valuable MVP) - which iteration is valuable. At any given point you are working on the aspect that is the most valuable e.g. User story mapping, prioritisation
9
Q
What are the 4 Delivery principles
A
- Get real using examples - customer not knowing what they want, but by showing them an example they may know e.g. Behaviour driven improvement
- Understand what is doable - understand scope, time, constraints (time, money and tech) e.g. Relative estimation, planning workshop
- Stimulate Collaboration and continuous improvement - with every iteration you understand the client and are more on point with the iteration for their needs e.g. collaborative games
- Avoid waste - every iteration is costly and time consuming e.g. lightweight documentation
