Methodologies and Frameworks Flashcards
1
Q
Framework
A
- The processes, tasks, roles, and guiding principles that form the structure of completing work.
- The framework significantly influences how a project moves from start to finish.
2
Q
What does DevOps promote?
A
Continuous integration, continuous delivery, and continuous deployment (CI/CD)
3
Q
Scaled Agile Framework (SAFe)
A
- Methodology used to expand Agile practices across multiple teams in an organization.
- SAFe is best suited for companies with projects involving multiple teams that need to communicate and collaborate effectively.
4
Q
Software Development Life Cycle (SDLC)
A
- Flexible framework designed to produce high-quality, low-cost, and thoroughly tested software through continual improvement.
- SDLC also relies heavily on thorough advance planning, which may not suit agile-focused teams
5
Q
Waterfall Methodology
A
- A sequential development process that flows like a waterfall through all phases of a project
- Initially used in manufacturing, and eventually made its way to software development because it was in common use by that time, serving as an early starting point.
- It follows a linear sequence
6
Q
What are the 6 phases of a Waterfall methodology?
A
- Requirements
- Design
- Implementation
- Testing
- Delivery
- Maintenance
7
Q
What are the advantages of Waterfall methodology?
A
- Waterfall framework is easy to understand and deploy
- The documentation required for these projects is very thorough.
8
Q
What are the disadvantages of Waterfall methodology?
A
- Not very flexible
- The plan is designed up front and changes or revisions down the line are often costly in time, money or other resources.
-Makes change management very expensive to conduct in a waterfall based project
9
Q
When would you use waterfall?
A
- Fixed requirements with no unknowns
- Change costs are very high
- Short and simple
10
Q
What is Agile methodology?
A
A project management approach that involves breaking the project into phases and emphasizes continuous collaboration and improvement.
11
Q
What are the differences between Waterfall and Agile?
A
Waterfall
- Structured and delivers value at the end
- Big design upfront approach
- Best with no unknowns
Agile
- Flexible and delivers value early and often
- Iterative and incremental
- Adaptable to change
12
Q
Iterative Development
A
- A software development approach that emphasizes the continuous refinement and improvement of a system or product
- The main goal of each iteration is to identify issues, make improvements, and incorporate feeback from users or stakeholders
13
Q
What are the key benefits of Iterative Development?
A
- Ability to respond quickly to changing requirements or emerging user needs
- Opportunity for early and frequent user feedback
14
Q
Incremental Development
A
- A software development approach that focuses on delivering small, functional parts of a system or product in a step-by-step manner.
15
Q
What are the key benefits of Incremental Development?
A
- Reduced risk and predictable project outcomes
- Developers manage complexity, minimize errors, and maintain a higher level of control over the developmental process
-Allows for faster delivery in new features
16
Q
What are the advantages of Agile?
A
- Adaptability
- Shorter release cycles
- Higher quality results
17
Q
What are the disadvantages of Agile?
A
- Potential scope creep
- Missed deadlines
- Less documentation
18
Q
What is Scrum?
A
Scrum is the most common agile framework; it delivers iterative and adaptive value while intentionally covering only the barest requirements.
- It uses empiricism and lean thinking to continuously improve results.
19
Q
What does Empiricism encourage?
A
For teams to make decisions based on what they see and know.
20
Q
What is Lean thinking?
A
It is focused on driving improved efficiency by reducing waste, redundancy, and other unnecessary work within a given project.
21
Q
What are the 5 Key Values of Scrum?
A
- Commitment
- Focus
- Openness
- Respect
- Courage
22
Q
What are the 3 Fundamental Pillars of Scrum?
A
- Transparency
- Inspection
3.Adaptation
23
Q
What are the 4 basic steps of the Scrum process?
A
- Product owner prioritizes work into a product backlog
- Scrum team selects the top items in the backlog
- Scrum team and stakeholders review the sprint results
- Steps repeat as long as the product backlog exists
24
Q
What are the 4 Roles in Scrum?
A
- Scrum Team
-Group of people who work together to deliver increments of value - Product Owner
-Creates, maintains, and owns the product backlog - Scrum Master
-The team’s coach which helps the team, product owner, and organization improve the implementation of scrum. - Developer
-Describes the remaining team members and isn’s exclusive to software engineers.
25
Product Backlog
An ordered list of product changes or enhancements
26
Product Goal
Describes the product's longer term target, and the product backlog should deliver the product goal.
27
Sprint Backlog
Includes what the team will do, why they think it is important, and how they will get it done.
28
Sprint Goal
Summarizes the value of the sprint
29
How many increments can a sprint have?
one or many
30
Sprint
Scrum iteration and the container for all other Scrum events
31
Sprint Planning
Lasts no more than eight hours for one month sprints, and even less for shorter sprints
32
Daily Scrum
Where the developers meet to review progress toward the sprint goal and then plan the next 24 hours of work.
33
Sprint Review
Uncovers issues early when they are small and easy to fix, reveals previously unknown development ideas, or confirms that the team is on track.
34
Sprint Retrospective
Occurs when the team inspects how they worked in the past sprint and identifies improvement opportunities.
35
What is the advantage of Scrum?
Scrum is flexible and can be used across any industry, and its short cycles allow for responsive learning and complex problem solving.
36
What are the disadvantages of Scrum?
- Scrum relies on the organization to respect the product owner's decisions about the backlog and priorities
- Scrum's framework is designed for a single, high-performing and cross functional team, which means that less-experienced teams may struggle and scaling up to larger groups might be difficult.
37
What is Scrum best suited for?
Highly cohesive, cross-functional teams that are focused on continual improvement
38
What is Kanban?
Kanban is used to control in progress levels, known as WIP levels, and manage workflows in software and business processes
39
What are the 6 Core Practices of Kanban?
1. Visualizing work: Create a Kanban board that shows the specific phases that work moves through on your team.
2. Limit work in progress: Prevents team members from getting overwhelmed and helps increase productivity and degradation of product quality.
3. Make policies explicit: Clearly define how work gets completed and moves from one phase to another.
4. Manage flow: This embraces the roots of lean manufacturing and reduces waste in the system.
5. Implement feedback loops: You bake feedback directly into the system and stay informed about performances
6. Improve collaboratively while evolving experimentally: This means that we need to use the scientific method to test ideas and measure the results in the Kanban signals.
40
What are the 3 phases that Work moves through?
1. To Do
2. In Progress
3. Done
41
What is the 4-part Workflow of Kanban?
1. the product owner prioritizes and orders the backlog
2. A team member selects the top-ordered item in the backlog and pulls it into progress
3. The team moves the work item through the workflow, keeping within the work in progress limits.
4. When the team is ready to start new work, they select the next item in the backlog.
42
What are the differences of Scrum and Kanban?
Scrum
- Helps teams solve complicated issues
- Better for unpredictable work
Kanban
- Helps teams focus on a reasonable amount of work
- Excels at most routine tasks
43
What do Scrum teams use to visualize their boards?
Kanban boards
44
What are Agile teams classified as?
1. Scrum
2. Kanban
3. Scrumban
45
What are the advantages of Kanban?
1. Kanban is the simplest agile framework to learn and can be applied to any industry
2. It's lightweight and focuses on routine work over iteration planning
46
What are the disadvantages of Kanban?
1. Kanban can be less effective if teams are oversized or have high turnover
2. Inaccuracies or changes between work items can disrupt the team's focus, and cycle times may stretch out in the absence of set iterations, if performance is not properly managed.
47
What is Extreme Programming?
(or XP) is another type of agile framework designed specifically for software development.
48
What are the 5 values in Extreme Programming Framework?
- Communication
- Simplicity
- Feedback
- Respect
- Courage
49
What are the 3 roles in Extreme Programming?
1. Customer: Decides which features are needed and which are needed next.
2. Tracker: Captures metrics, measures progress, and looks for improvement opportunities
3. Coach: Mentors team members on how to use Extreme Programming practices
50
Most Common Practices in Extreme Programming
-Paired Programming: 2 software engineers work side by side to create code at once.
-Ten Minute Building: States that it should take less than 10 minutes to build, test, and deploy an entire system.
-Continuous Integration: Merges local code into the main repository at least a few times each day.
-Test First Programming: A practice where developers write tests and then write code to pass the tests
51
What are the advantages of extreme programming?
-Very efficient
-Continuous integration, automation, and high rate of adaptability
-Team-focused practices and less project failures
52
What are the disadvantages of Extreme Programming?
- Has limited scope
- Code - centric practices can result in less optimal design
- Rapid pace of the work can cause stress
- Minimal documenation can hinder new team members' understanding
- Relies on face-to-face interaction between team members and customers
53
What is DevOps?
A set of practices and tools that integrates and automates the work of software development and IT operations as a means for improving and shortening the systems development life cycle.
54
What are the 2 categories of the Software Delivery Process?
1. Software Development: The development team designs and creates software across four workflow phases: plan, code, build, and test.
2. IT Operations: The operations team would then deploy and support software across the four workflow phases of release, deploy, operate, and monitor.
55
Continuous Integration (CI)
Individual developers check their code into the main branch frequently, and automated tests run against the new code.
56
Continuous Delivery (CD)
Prepares the code for release to production.
57
Continuous Deployment (CD)
After integration, the continuous deployment process prepares the code for production release and deploys it to production.
58
What are the strengths of DevOps?
- Great for teams that want to release code often
- Companies that want to limit friction
- Organizations with the resource to staff cross-functional teams
59
What are the weaknesses of DevOps?
- Require significant expertise and groups may struggle to find enough team members with the necessary skills
- Large or legacy systems with minimal automation will find it difficult to quickly switch over to DevOps.
59
Scaled Agile Framework (SAFe)
A methodology used to expand Agile practices across multiple teams in an organization.
Strikes a balance between keeping teams aligned and preserving the team's autonomy.
60
Scaled Agile
Term used to describe any methodology that expands agile tools to more than one team
61
Agile Team
Teams are made of three to ten cross-functional people working together to deliver increments of value
62
Agile Release Train (ART)
Groups the related teams to simplify communication, planning, and schedules
63
Iteration
Agile methodology iteratively develops a product in fixed time increments
64
Program Increment
- Similar to a quarterly cycle in extreme programming, and it serves as a long-term planning cycle
- Lasts 8-12 weeks instead of 3 months
- It is a shared timebox for all the teams on an ART
65
Program Increment Planning
Serves as the ART's planning event and is similar to sprint planning for a single Scrum team.
66
Strength of SAFe
SAFe is great for bringing the benefits of agile to a larger organization and meets the scaling needs of scaling
67
Weakness of SAFe
Needs to add layers of terms, overhead, organization, and staff, which can grind the gears of Agile's ground-up approach.
68
Software Development Life Cycle (SDLC)
- A flexible software development framework that aims to produce high- quality, low-cost, and thoroughly tested software.
SLDC users incorporate best practices and lessons learned into the framework to be more efficient every subsequent cycle
69
What are the 7 phases in the SDLC Framework?
1. Planning: Where we outline the project and define the software's scope and purpose
2. Requirements: We define the resources needed for the project and determine what the software needs to do
3. Design and Prototyping: Defines how the software needs to work, such as which programming language to use, which security protocols to use, and how the user interface behaves
4. Development: When the software is actually created
5. Testing: When tests are carried out to ensure the software performs as expected
6. Deployment: When the software enters production
7. Operations and Maintenance: When the software is supported as long as it remains in production
70
71
