Explore topic-wise InterviewSolutions in Current Affairs.

DIFFERENT project management TOOLS used in Agile are: 

• Icescrum 
• Rally Software 
• AGILENT 
• Version One 
• Agilo 
• X-planner 

A product roadmap, as the name suggests, is a powerful TOOL that DESCRIBES how a product is likely to grow over time. It is a HOLISTIC view of product features that create the product vision. It also indicates what DEVELOPMENT is building, business goals that the new product will achieve, problems that the product will solve, etc. A product roadmap is owned by the product manager. It also encourages the development team to work together to achieve the desired goal for the SUCCESSFUL delivery of the product.

Iterative Development: It is basically a software development process where software development cycles (sprint and releases) are repeated until the final product is obtained. On the basis of feedback from customers or users, the product is again developed in cycles or releases and sprints i.e., adding new functionality in a repetitive MANNER. 
Incremental Development: It is basically a software development process where development WORKS are SLICED into increments or pieces or PORTIONS. In this, the software is developed and delivered in pieces or increments and each piece has a complete set of functionalities. The increment can either be small or large, and each increment is CODED and tested fully. After testing each increment, they all are integrated so that they work as a whole. 

A daily stand-up meeting is a day-to-day meeting among all the members of the AGILE team. Its main purpose is to know the current progress and PERFORMANCE of every team MEMBER that works on Scrum tasks. The meetings take place mostly in the morning and usually involves product owners, developers, and the scrum master. 

These meetings usually take place for the following reasons: 

• To know what was done yesterday and what is the plan for TODAY. 
• To provide a better UNDERSTANDING of goals. 
• To make sure that every team member is working toward the same goal. 
• To bring problems of team members into focus so that problems can be addressed quickly. 
• To bring everyone up to date on the information and help the team to stay organized. 

A velocity is basically a MEASUREMENT unit that measures or calculates how much work an agile development TEAM can successfully complete in a single sprint and how much time will be required to finish a project. It is widely used as a calibration tool that helps development teams to create accurate and efficient timelines. It is also used to IDENTIFY PROBLEMS and measure the IMPROVEMENTS that occur with time.

Agile Software DEVELOPMENT: It is an iterative approach that is used to design complicated software. In this method, project teams are allowed to be more flexible and ensure that the final is fulfilling the customer’s requirements. It develops customer-centric products and delivers in shorter SPRINTS. 

Traditional Software Development: It is a linear approach that is used to design simple software. In this method, all the phases of the process usually occur in sequence. It is more suitable for projects where the possibility of changes is negligible in the scope.

Spike: It GENERALLY refers to a too large and complex user story in software development that cannot be estimated until the development team runs a timeboxed INVESTIGATION. These STORIES can be used for various activities like RESEARCH, design, exploration, prototyping, etc. Spikes are usually created to resolve some technical issues and design problems in the project. 

Zero Sprint: It generally refers to the first step or pre-preparation step that comes just before the first sprint. It includes all activities such as setting a development ENVIRONMENT, preparing backlog, etc. 

Sprint Backlog: It is generally owned by the development TEAM. It only contains those features and requirements that are related to the specific sprint only. It is considered a subset of the product backlog. It is compiled of everything that MUST be done to complete a particular sprint. It only includes items that can be completed during each agile sprint. It is specific to the sprint goal only in a particular sprint. 
Product Backlog: It is generally owned and MAINTAINED by the project owner. It usually contains each and every feature of the product as WELL as the requirements of the product. It is compiled to everything that must be done to complete the whole PROCESS. It just breaks down every item into a series of steps. It is more specific to the end goal of the product. 

Re-factoring is basically an activity that involves alteration or MODIFICATION of the internal structure of SOFTWARE without any change in its external behaviors or FUNCTIONALITY. In this, developers make some changes or tinker with CODE to enhance and improve the internal structure of software. One of the most popular and widely used refactoring techniques in the agile software development process is Red-Green. The refactoring process makes the code more readable, understandable, and clean. The continuous habit of refactoring helps to make it easier to EXTEND and maintain code. 

There are several good qualities an Agile tester should have. Some of them are listed below: 

• Positive attitude and solution-oriented 
• Focused towards goal 
• EXCELLENT communication skills  
• Understand and fulfill customer requirements 
• Basic knowledge about the Agile process and its PRINCIPLES 
• Critical and CREATIVE thinking 
• Share IDEAS effectively 
• Plan and prioritize work on the basis of requirements 
• COPE up with change

Agile testing, as the name suggests, is a software testing process where software is tested for any defects, errors, or other issues. It is considered a core part of the development process as it ENABLES testers and developers to work together as a team that in turn improves overall performance. It also helps in ENSURING the successful delivery of high-quality products. Testing is usually PERFORMED so that testers can identify and resolve the problems early and at every point in the development process.

Principles of Agile Testing 

There are eight main principles of Agile Testing as given below:

• Continuous Testing: Testing should be conducted continuously by the Agile team to ensure continuous development progress.  
• Continuous Feedback: This process generally encourages taking feedback from clients to make sure that the product meets the requirements of the client or customer.  
• Team Work or collective work: Not only testers but developers, business analysts can also perform software testing or application testing.  
• Clean Code: Quality of software is maintained as the team tests the software to ensure that the code is clean, simple, and tight. All errors and defects that are found during the testing phase are fixed quickly within the same iteration by the Agile Team. 
• Less Documentation: This process usually involves the usage of reusable checklists instead of lengthy documentation.  
• Test-Driven: In other CONVENTIONAL methods, testing is only performed after the implementation but in agile testing, testing is done during the implementation so that errors or any issues can be removed on time.  
• Customer Satisfaction: During the agile testing process, development progress is being shown to clients or customers so that they can adapt and update their requirements. This is done to ensure customer satisfaction.  

Advantages 

There are several advantages of using the AGILE Process as given below: 

• Adapt well with changing requirements 
• Face-to-face conversation with team members and customers 
• Focuses on technical excellence and good design 
• Fast and continuous DEVELOPMENT  
• Enables collaboration and interaction between client and project team 
• Ensure and promote customer satisfaction 
• Faster feedback from customers or end-users 
• Quick identification and elimination of errors found in the code  
• Division of agile project into sprints or iterations i.e., short and repeatable phases typically 1-4 weeks LONG 
• Quick delivery of products  
• Easy to manage with more flexibility  
• The end goal can be unknown: Agile is BENEFICIAL for projects where the goal is not defined and as the project progresses, the goal becomes more evident. 

Disadvantages 

There are several disadvantages of using Agile Process as given below: 

• Lack of formal documentation and designing 
• Difficult to estimate resource requirement and effort  
• Not good for small development projects 
• Costly as compared to other development methodologies 
• REQUIRES more time and energy from everyone 
• Risk of ever-lasting project 
• Difficult to scale large projects 
• Difficulty in testing and test construction.

Different types of Agile methods or frameworks widely used in the world for software development and project development are listed below: 

• Scrum: It is used to establish hypotheses, test them, reflect on the experience, and also make adjustments. It heavily depends on feedback, self-management, small teams, and work broken out into sprints. It relies on incremental development. 
• FDD (Feature-Driven Development): It generally INVOLVES creating software models every two weeks and also needs development and design for each and every model feature. It is basically a lightweight iterative and incremental software development process whose MAIN purpose is to deliver stable and working software on time.  
• Lean Software Development: It is basically a way of minimizing waste and maximizing value. It is more focused on process efficiency for optimum results in customer value. It is totally based on two guiding principles i.e., respect for people and continuous improvement. 
• XP (Extreme Programming): Its main purpose is to produce higher-quality software and higher quality of life for the development team. It is considered low-risk, flexible and a way to develop software and ensures that clients get what they require. In this methodology, the software is tested RIGHT from day one, collecting feedback so as to improve the development process. 
• DSDM (Dynamic Software Development Method): It generally focuses on the full project lifecycle and the main aim is to ensure good governance as the foundation for project management. It is user-driven and believes that modifications to the project are always expected. It also provides a full roadmap to deliver products on time and within budget.  
• ASD (Adaptive System Development): It represents the idea that projects should always be in a state of continuous adaptation, and has a cycle of three repeating series i.e., speculate, collaborate, and learn.
• Crystal Methodology: It MAINLY focuses on individuals and their interactions RATHER than processes. It is considered one of the most lightweight and flexible approaches to developing software. It is a family of agile methodologies that include different variants such as crystal clear, crystal yellow, crystal orange, and crystal red. 
• Kanban: Kanban projects are generally managed through a board or table (Kanban Board). This Kanban board is a tool that helps team members to keep an eye on workflow for measuring its progress and includes all the information that is needed to be done on the product at each stage along with its path of completion. Its main purpose is flexibility in task management, continuous improvement, and enhanced workflow.