In continuation of my previous blog [#6] on this subject following questions and answers are continued:
1. During test driven development [TDD] what are the main tasks need to be considered ?
Ans: During TDD, the following tasks need to be considered:
- A test first approach need to be facilitated while iteration requirements are being drafted or during model storming activity.
- The test approach points need to be converted into software specifications to design and develop the software code.
- Finally a concrete test case finalization can happen during TDD process.
- Make a Plan to write the code in a testable approach.
2. What is review activity in a project and where all you can have this activity ?
Ans: The Review need to be done against on any output of the activity. Before starting an activity we need to have the base item to work on that activity to complete. Once it is completed the review need to be performed to identify the potential issues. This need to happen across the Agile project activities. The review can be formal or informal depends on the need or situation.
3. What is a code refactoring ?
Ans: In any software code or program, the future requirements need to be ammended. The written instructions need to be flexible to adopt the new steps to accommodate easily in the existing code. If this facility is not available in the code, the new or old developer need to restructure the code to accommodate these amendments. In every code the reusable component or functions insertion is the best practice to utilize for future requirements.
This method is called code refactoring. Many legacy systems, those were coded on ad-hoc basis need to be under code refactoring activity. The Agile process steps can be implemented if the code refactored or if the software has reusable modules. This way the developers or any technical teams can delivery the SPRINT items faster.
To have some understanding on building reusable code please see my videos which has an e-commerce scenario example: https://www.youtube.com/watch?v=zCR6GP1ji60
4. What is Scrum and how it helps in Agile development cycle?
Ans: Scrum is an incremental and iterative software development process/framework in Agile software development. It makes the development team as integrated team to work on a common goal. The teams are also collaborated and mixed together with this process to work on common goals. This way it helps Agile SDLC to deliver the workable software.
5. How the teams are expected to work in a Scrum process ?
Ans: The teams are expected to work in a self organized way. They are also expected to co-locate to one place or through online collaboration within the teams to work closely and to have daily face to face communication with a disciplined approach to reach the goal.
6. How to handle the Requirements volatility in Scrum Process ?
Ans: In a Scrum process the key principle is to accept the requirements changes during the product development. Hence at any given time before deploying the product into production the users can demand for any change and the technical team need to accept it. Hence there is a facility to handle the Requirements volatility in Scrum Process.
7. During the scrum process how the problem definition and its acceptance can be adopted ?
Ans: In Scrum, with multiple iterations the product development is driven. The details of product final goal or vision is not known in one iteration. Once all the iterations are defined only, these symptoms can be known. In the beginning of the project or during requirements envision phase the iterations need to be defined in high level with requirements segregation. Then the iterations clarity need to be available to accept for construction during the SPRINTs making. Then the acceptance criteria is known to the teams to adopt into delivery process for different SPRINTs.
8. How the Scrum Model works ?
Ans: The Scrum model works in the following approach:
- By focusing on maximizing the team’s ability to deliver quickly.
- The response for emerging requirements should be faster.
- More adoption to evolving technologies.
- Adopting changes towards the market conditions.
9. Whom all the Product owner represents during Scrum process ?
Ans: Product owner represents the Product stakeholders and the voice of the customer.
10. What for the Product owner is accountable in a Scrum process ?
Ans: The Product owner [PO] is accountable to ensure the teams deliver the value to the business.
Please feel free to contact for any support.