Se
Lernkarteien
Lernkarteien
Kartei Details
Karten | 47 |
---|---|
Sprache | English |
Kategorie | Technik |
Stufe | Andere |
Erstellt / Aktualisiert | 25.11.2022 / 21.02.2023 |
Weblink |
https://card2brain.ch/box/20221125_se
|
Einbinden |
<iframe src="https://card2brain.ch/box/20221125_se/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
What are 2-3 conditions that need to be in place for scaling agile to get off for a good start?
- Management Buy-In
- Small experienced team
- Management position to get things going
- Work with management
- Start with 2-3 teams
- Continous Learning
What does SAFe stand for?
Scaling Agile Framework
What are the main points of the agile manifesto?
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
What are the 12 principles of agile software?
- Satisfy customer through early delivery
- Welcome changing requirements
- Deliver frequently
- Business people and developers work together
- Motivated individuals...
- Face-to-face conversation
- Working software
- Sustainable development
- Attention to technical excellence
- Simplicity
- Self-organizing teams
- Regular self-reflection
Why do we estimate? Name 4 reasons.
- To plan
- To schedule (f.e. releases)
- Plan ressources (or hire them if needed)
- Price and guide investment
Explain Planning Poker and its steps
It's a method for estimating story points. The SM sits together with the development team:
- SM picks a task and reads it to the development team
- Each teammember picks one of his planning poker cards which states "how big" the tasks is in his/her opinion.
- The cards are shown (turned public) all at once.
- If the whole team agrees good. If the estimate vary heavily, the "player" with the highest amount and one with the lowest one justify their picks (on why this tasks takes that long)
- The estimates are continued until theres consens.
What is the Sprint Backlog and who is responsible for it?
A list of all User Stories and Tasks that the team wants to complete in the current sprint.
The team is responsible for it.
What are Story Points and why are f.e. Fibonacci Numbers used for it?
A relative work estimate to other User Stories.
Fibonacci Numbers are used because large numbers reflect the uncertainty, for which the team estimated certain User Stories.
Name 3 agile process models
- Scrum
- XP
- DevOps
Name 3 traditional process models
- Waterfall
- V-Model
- RUP
Is Kanban a Pull- or Push-System? What's the difference?
Kanban is a Pull-System
Steps of the process pull work that has been completed in the prior step to their "group", rather than the issue being pushed into the next step upon completion.
What is "Lead Time" in Kanban and why is it important?
Lead time is the time it takes from an issue appearing till its completion / delivery to the customer.
It's a metric which shows how efficient your timeline is. If the lead time is too high, it means that there are to many issues being worked on and they're not completed. Fix it with a WIP Limit, by increasing capacity or efficency or stop taking new issues.
What is "Cycle Time" in Kanban and why is it important?
It's the time a tasked is actually processed. From In Progress to Done
What does WIP Limit (Work in progress limit) mean in Kanban?
It's lmiting on how much tasks is being worked on simultaniously.
What is Throughput in Kanban?
Throughput per Unit of time is the average of item produced in a given time period.
Can be compared to velocity (Scrum)
What does the principles and practices of Kanban mean to Software Development
- Transparency is important and useful
- Can manage the workflow better
- Kanban optimizes the workflow
- Happier Staff
What is a burndown chart?
How quickly a team is achieving the User Stories
Viewed as how much more is left to complete over time within a Sprint iteration
What is a burnup chart?
How quickly a team is achieving the User Stories
Viewed as how much has been done over time within a Sprint iteration
What is velocity?
The number of story points a team can complete during / or has completed in the past of an iteration
What are the metrics (Burndown, Burnup, Velocity etc.) used for in Scrum?
Enables the team during Sprint Planning to determine how much they can commit to, based on past iterations.
Remarks:
- Don’t use the metrics to blame any team!
- Can’t compare Velocity of Team A : B!
What is Scrum?
SCRUM is an agile, lightweight process for managing and controlling software and product development in changing environments.
What are the different roles in Scrum?
- Core Roles
- Product Owner
- Scrum Master
- Development Team
- Other Roles
- Users
- Management
- other Stakeholders
What are the characteristics of Scrum?
- Self-organizing teams
- Product progresses in a series of one- to four-week “sprints”
- Requirements are captured as items in a list of a “product backlog”
- No specific engineering practices prescribed
- Uses generative rules to create an agile environment for delivering projects
What are Sprints in Scrum
- Scrum projects make progress in a series of “sprints”
- Typical duration is 2–4 weeks or a calendar month at most
- A constant duration leads to a better rhythm
- Product is designed, coded, and tested during the sprint
What are the responsibilites of the Product Owner?
- Define the features of the product
- Decide on release date and content
- Be responsible for the profitability of the product (ROI)
- Prioritize features according to market value
- Adjust features and priority every iteration, as needed
- Accept or reject work results
What are the responsibilites of the Scrum Master?
- Represents management to the project
- Responsible for enacting Scrum values and practices
- Removes impediments
- Ensure that the team is fully functional and productive
- Enable close cooperation across all roles and functions
- Shield the team from external interferences
What are the responsibilites of the Development team in Scrum?
- Builds the product that the Product Owner indicates
- To deliver the potentially shippable product each Sprint
- A very high degree of autonomy and accountability.
- The Team decides what to commit to, and how best to accomplish that commitment;
- Typically 5-9 people
- Cross-functional, i.e. Programmers, testers, user experience designers, etc.
- Teams are self-organizing
- Membership should change only between sprints
What are the different Ceremonies in Scrum?
- Sprint Planning
- Sprint Review
- Sprint Retrospective
- Daily Scrum
What is being done in Scrum sprint planning?
- Team selects items from the product backlog they can commit to completing
- Sprint backlog is created
- Tasks are identified and each is estimated (1-16 hours)
- Collaboratively, not done alone by the Scrum Master
- High-level design is considered
How is the Daily Scrum organized?
- Parameters
- Daily
- 15-minutes
- Stand-up
- Not for problem solving
What is being done in Sprint review and who participates?
- Team presents what it accomplished during the sprint
- Typically takes the form of a demo of new features or underlying architecture
- Informal
- 2-hour prep time rule
- No slides
- Whole team participates
- Invite the world
- Onle “Done’s” are presented
What is being done in the Sprint retrospective?
- Periodically take a look at what is and is not working
- Typically 15–30 minutes
- Done after every sprint
- Whole team participates
- Scrum Master
- Product owner
- Team
- Possibly customers and others
- For example
- “Start / Stop / Continue”
- “Good / Could be better/ Measures”
What are possible Scrum Artefacts?
- Product Vision
- Sprint Goal
- Product Backlog
- Sprint Backlog
- Definition of Done
- Burn-Down Chart
- Increment
- Burn-Down Chart
For which project size are agile models predominantly?
Traditionally for smaller projects due to planning uncertainties.
For which project size are traditional models predominantly?
Great for big projects or projects, that are low risk. There's lots of overhead in smaller projects though.
How are Requirements handled in agile models?
Requirements are changed as necessary. Begin Development as soon as possible (when MVP-Requirements are available)
How are Requirements handled in traditional models?
Define requirements in the beginning and after verification, built the entire system.
Define process / measures for Change Management in order to change the requirements. Generally less open to change.
How is planning done in agile models?
Only plan 1 sprint / iteration at the time. See which tasks get completed and then continue.
How is planning done in traditional models?
Plan every milestone in advance. Attempt to never change the planning again.
What means INVEST for User Stories?
What does it stand for and why is it important?
A good user story should be:
- “I” ndependent (of all others)
- “N” egotiable (not a specific contract for features)
- “V” aluable (or vertical)
- “E” stimable (to a good approximation)
- “S” mall (so as to fit within an iteration)
- “T” estable (in principle, even if there isn’t a test for it yet)