Explore topic-wise InterviewSolutions in Current Affairs.

Agile Metrics are basically standard metrics that are used to MEASURE the work of the team. These metrics are used to determine the quality of work, productivity, progress, team health, etc. Its main focus is on value DELIVERED to customers and how much end-users were impacted by it. 
Standard Metrics for the Agile project 

• Velocity: It measures the amount of work done by the development team during a sprint. It gives ideas about progress, capacity, etc. 
• Cumulative Flow Diagram: It is a flow diagram used to measure the CURRENT status of work in progress of the team. It is simply used to track the progress of agile teams and manage flow stability. 
• Defect Removal Awareness: It is used to measure the ability of the development team to remove defects prior to release. It helps to maintain the quality of products by a working team. 
• Work Category Allocation: It is used to measure where we are spending or investing our time so that we can adjust our priorities. 
• Sprint Burndown Metric: It is used to measure the total number of sprints or tasks that are completed as compared to estimated scrum tasks. It usually tracks the progress being made on tasks during a Sprint.  
• Defect Resolution Time: It is used to measure the time taken by the team to identify and fix the defects or bugs in the software. There are several processes involved in fixing bugs. 
• Time Coverage or Code Coverage: It is used to measure the time that is GIVEN to code during testing. It helps one to UNDERSTAND how much code is tested and also helps in assessing the test performance. 
• Business Value Delivered: It is used to measure the efficiency of the working team. 

The increment is simply the sum or total of all the product BACKLOG items that were COMPLETED during a sprint and the value of increments of all previous SPRINTS. It is the total work completed within the CURRENT and previous sprints.

• Sprint Planning Meeting: In this meeting, the discussion takes place about features and product backlog items (user stories) that are important to the team. This meeting is usually attended by the product OWNER, Scrum Master and Scrum Team. It is a weekly meeting and usually lasts for about an hour. 
• Sprint Review Meeting: In this meeting, the Scrum team gives a demonstration of the product. After this, the product owner determines which items completed and which are not completed. He also adds some additional items to the product backlog on the basis of feedback from customers or stakeholders. Its MAIN aim is to inspect the product being created in the sprint and modify it if required. 

• Sprint Retrospective Meeting: This meeting takes place after the Sprint planning meeting. In this meeting, the Scrum team meets again to inspect itself and discuss the PAST mistakes, potential issues and methods to resolve them. Main aim of this meeting is to improve the DEVELOPMENT process. This meeting lasts for about 2-3 hours. 
   

Planning Poker, also KNOWN as Scrum Poker, is a consensus-based technique that not only helps agile teams to estimate the time and effort that is required to complete each initiative on their product backlog but also identifies issues before time and within the course of a user story. It makes the meeting more SHORT, productive and creates estimates with the involvement of the whole team. It is mainly USED to avoid the influence of other PARTICIPANTS, and force each person to think independently and give their opinion. 

Three main AGILE FRAMEWORKS other than Scrum are: 

• KANBAN 
• Test-Driven Development (TDD) 
• Feature Driven Development (FDD) 

Different types of Burn-Down charts are listed below: 

• Product Burndown Chart: It is a TYPE of chart that is used to show story POINTS of each completed sprint so that it depicts the completion of requirements over time. It mainly shows how many of the product goals are being achieved by the team and how much WORK is remaining. 
• Sprint Burndown Chart: It is a type of chart that is used to show the remaining works for the scrum team of a particular sprint. It makes the work of the team VISIBLE and shows the rate at which work is completed and how much is remaining to be completed. 
• Release Burndown Chart: It is a type of chart that is used to show how a team is progressing against the work for a release. This chart is updated by the scrum team at the end of each sprint. It is very ESSENTIAL to see what process is being made during each sprint. 
• Defect Burndown Chart: It is a type of chart that is used to show the total number of defects that are being identified and fixed or removed. 

Burn-up Chart: It is a type of chart that is used to display or represent the AMOUNT of work that has been completed and the total amount of work for a SPRINT or ITERATION.   
Burn-down Chart: It is a type of chart that is used to display or represent the amount of work that is remaining to be completed in the project. These charts are very SIMPLE and easy to understand.  

The agile manifesto is basically a document consisting of values and principles that are expressed in Agile. It was created in early 2001. It simply consists of 4 values and 12 key principles. This manifesto helps the development team to work more efficiently and provides a CLEAR and measurable structure that promotes team collaboration, iterative development, etc. It is specially designed to improve development methodologies. 
The 4 Agile Values  

1. Individuals and INTERACTIONS over Processes and Tools: It focuses on giving more attention and importance to communication with clients.
2. Working Software over Comprehensive Documentation: It focuses on the completion of the project and making sure that the project is completing the final deliverables.
3. Customer Collaboration over Contract Negotiation: It focuses on involving customers in all phases of the project so that the final product doesn’t lack any requirement that the client needs. It is done to ensure 100% customer satisfaction.
4. Responding to Change over Following a Plan: It focuses on changes and motivates the team to adopt the change quickly so that higher quality products can be delivered. Therefore, agile WORKS in short sprints so that changes can be utilized for good.

The 12 Agile Principles 

1. Customer Satisfaction: First priority is to fulfill customer demands to ensure 100% customer satisfaction.
2. Welcome Change: Changes are important for improvement therefore even late in the development process, changes can be introduced and addressed throughout the development period.
3. Deliver Frequently: Products have to be delivered as soon as possible therefore focus on a shorter timescale.
4. Work Together: Both business stakeholders and team members work together through the development process for better collaboration.
5. Motivated Team: For delivering high-quality products, team members are motivated and ENCOURAGED. Team members are given the environment and support they need to perform effectively.
6. Face-to-Face:  Agile emphasizes Face-to-face communication which is the most effective and efficient way of conveying information. It helps the team to communicate simple and complex information in an effective way.
7. Working Software: Delivering working software to the customer is the major concern of Agile. Working software or product is the primary measure of progress towards the final product.
8. Constant Pace: Agile promotes sustainable development. All teams, sponsors, developers, and users that are involved in the agile process should maintain a constant speed to deliver working software in a short timescale.
9. Good Design: Focuses on good design and technical details to improve quality and agility (quick and graceful).
10. Simplicity: Team focuses on tasks and features that are essential and reduces the amount of work and time spent on complex features and tasks that are not essential. It is done to keep things simple.
11. Self-Organization: Agile team should be cross-functional and self-organized. It should not depend on the manager to assign work, instead should find their own work and manage the responsibilities and timelines. Such teams not only help to deliver good quality software but also provide the best designs, requirements, and architectures.
12. Reflect and Adjust: To improve the effectiveness of a team, the team reflects on how to become more effective and ASSESS their working style at regular intervals. This is done so that one can learn from their mistakes and take some steps to improve their performance in the next iterations.

Pair programming, as the name suggests, is a type of programming where two people write code together and work side-by-side on one machine or computer. It is basically a TECHNIQUE mostly used in agile software development. In this type of programming, one person writes code and ANOTHER person checks and REVIEWS each line of code. Both of them also switch their roles while doing work. 

Advantages of Pair Programming

•  Develop higher-quality code 
• Reduce the risk of errors 
• An effective way to share knowledge  
• Enhanced productivity 
• Improved TEAM collaboration 

Agile: It is an approach mainly used for software development. In this methodology, complex projects are broken down into smaller units that are achievable in a specific time frame. It always involves customers in the development process. 
Scrum: There are different agile methodologies, and Scrum is one of them. It promotes accountability, function, and teamwork SIMILAR to Agile. In simple words, it is an improved way of Agile methodology and shares the same PRINCIPLES and values of Agile with adding some of its own unique features.  
Agile vs Scrum
Agile and Scrum, both provide a flawless EXPERIENCE to customers in the software development cycle and share similar methods like collaborative iterations. But STILL, both of them cannot be substituted for each other. It mainly depends upon the type of project, budget, time, and feasibility to choose any one of them for project development.  There are several differences between them as given below: