Yamini Munipalli

This article addresses a process where a team moved from a traditional waterfall model to using agile elements in order to deliver a product to a government agency. It talks about typical problems that come up in a transition to agile, complications from distributed teams, and the advantages and disadvantages of the process for government or nongovernment clients.

This paper discusses the day-to-day activities of a tester instilling quality into software. It begins with a foundation-level discussion of software testing and quality assurance. Then Yamini discusses how the two relate to each other. Afterward, she explains the daily tasks involved in software testing and Quality Assurance, some pain points and areas for improvement, and how an individual tester can add value to the development process no matter what type of software development life cycle is governing your environment.

In this article, Yamini Munipalli discusses the issue of whether the selection of automated tools should come before the development of QA processes in an organization. She presents her experience with this issue and hopes to shed some light on why automated tools should be secondary.

The concept of risk is inherent in any development effort. Since risk is impossible to avoid, the best way to deal with risk is to contain it. One way to contain risk is through risk management. Risk management involves the identification of risks, analysis of exposure to the risks in a development effort, and execution of the risk management plan. In this article, Yamini Munipalli details one way of assigning and managing risk to a software development plan. This version of risk analysis, drawn from many schools of thought, remains flexible enough to use within any company for any project.