Traceability Matrix: How to Map Requirements to Test Cases

Refer to following articles for more:

•  Traceability Matrix: How to Ensure the coverage of Requirements in Test Cases
•  FAQs about UAT (User Acceptance Testing)
•  Project Planning: How to Design the Project Flexibility Matrix
•  How to Develop a Software Change Management Process and Governance
•  How to Prepare Workflow Diagram and Systems

When you write test cases from a requirement document or use case document, you should remain sensitive towards the coverage of the requirement and converting them to testable items. The test cases are designed keeping in mind about the requirements coverage. If there are areas not covered in the test case, it will go untested. In order to verify whether all the requirements are being tested or not, Traceability Matrix is created. It maps requirements to the test cases.

How to Work in TDD Methodology of Software Development

Test Driven Development methodology of software development is one of the most popular flavor of agile methodology. Other popular flavors of agile are Scrum, Extreme Programing (XP), Function Driven development (FDD) etc. The main principle behing TDD is to write unit test cases first and then code the unit of the module so that the unit passes the test. TDD saves a lot of time and money in finding the sofwtare defects at the later stage of software development. Farther the testing cycle falls, higher would be the cost to fix the issue.

How to Conduct Performance Evaluation of Agile Team

Traditional performance measurements are successful with the traditional methodology of software development, where we stress more on individual contributions towards creating the software and reporting is made hierarchical in nature. In agile, the evaluation must also be adaptive, collaborative and frequent.

The traditional performance evaluations focus more on the individual performance and training needs. Whereas, in cross-functional team of agile evaluation of only individual performance would not be fair. So what stand should you take in such a case?

How to Measure Agile Team Members' Performance

The key elements of agile (say Scrum) methodology of software development is the team is cross-functional, collaborative and self-organized. Means, in Scrum, the entire team is responsible to execute the Sprint tasks; not the individual member of the team. So, the success or failure of the Sprints is based on the cumulative performance of the team. There is, however, a problem in judging an individual's performance; because each team member is not highlighted much during the product development.

How to Conduct Daily Scrum Meeting

Daily stand-up meeting is one of the most critical meetings in agile methodology of software development. It is a quick review of each team member's last days work, planning for the next day's work and impediments the member is facing. ScrumMaster looks into the impediment and can resolve it upfront or in a sidebar meeting.

Role of the Product Owner in Scrum (Agile)

In Scrum, one of the flavors of agile methodology of software development, there are three fundamental roles: the Product Owner, The ScrumMaster and the team. In current post let us talk about the Product Owner's role in detail.

The Product Owner represents the customer's interest and prioritizes the backlog of tasks according to the business needs. She/ he participates in the Sprint Planning meeting and evaluates the entire product backlog, prioritizes them and include in or exclude from the next Sprint. She/ he has the final say whether the task should be reprioritized or dropped. The team working on the product development can negotiate with the Product Owner on the priority of the task, but the final discretion lies with the Product Owner only. The Product Owner also decides the acceptance criteria for the potentially shippable product after the Sprint is completed.

Defining Impediments in Scrum (Agile)

Impediments are the roadblocks or hindrances faced by the team in agile methodology of software development. To make the definition look more clear and practical, impediments are any causes which will delay team's deliverables or stop from progressing in a task and eventually costing the team's productivity.

 

Role of ScrumMaster in Scrum (Agile)

 

In Scrum, one of the flavors of agile methodology of software development, there are three fundamental roles: the Product Owner, The ScrumMaster and the team. In current post let us talk about ScrumMaster's role in detail.

ScrumMaster acts as a facilitator for the team and is co-ordinator between the Product Owner and the team. He also co-ordinates with the management and the company's support functions to remove any roadblocks or impediments faced by the te team. Typical "command and control" style of management does not produce results for the ScrumMasters. In fact, there is no place for such a manager in agile.