Software Testing (2)

content

• Pick 1 of the 12 principles of the Agile Manifesto that interests you for risk assessment
  • 12 principles of agile development
  • risk assessment
  • Pick 1 of the principles for risk assessment

---

Pick 1 of the 12 principles of the Agile Manifesto that interests you for risk assessment

---

12 principles of agile development

1. Our most important goal is to satisfy our customers through early and continuous delivery of valuable software
   .
2. Changes to requirements are welcome - even late in project development. Be good at taking advantage of changing requirements to
   help customers gain a competitive advantage.
3. Continuously deliver usable software, with cycles ranging from weeks to months, the shorter the better.
4. Business people and developers work together on a daily basis throughout the project.
5. Motivate project people, build the project around them, give them the environment and support they need
   , and trust them to get the job done.
6. The most effective method of communication, both within and between teams, is face-to-face.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. Project parties, developers and users should be able to maintain a
   constant and stable rate of progress.
9. Refinement of technology and continuous refinement of design will increase agility.
10. Keep it simple. Simplicity is the art of reducing unnecessary work as much as possible.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. Teams regularly reflect on how they can be more effective and adjust their behavior accordingly.

---

risk assessment

1. Requirements change risk.
2. Schedule risk, budget risk, management capability risk, information security risk.
3. Application technology risk, quality control risk, software design and development tool risk, employee skill risk.
4. Human resource risk, policy risk, market risk, marketing risk.

---

Pick 1 of the principles for risk assessment

---

Continuously deliver usable software in cycles ranging from weeks to months, the shorter the better

• Requirements change risk
  The third principle of agile development requires that software be delivered in as little time as possible, because user requirements may change over time. Delivering software as soon as possible can reduce engineering problems caused by sudden changes in customer requirements in the middle of development. Process is severely affected.

• Schedule Risk
  Delivering the software as early as possible can ensure the smooth completion of one of the stages, and avoid user requirements changing due to long development time and market influence, which will affect the progress of the entire project.

• Budget risk
  The longer the development cycle, the more manpower and material resources are invested, and the greater the funding required. Therefore, the shorter the development cycle, the more the budget risk can be reduced.

• As the development time increases, the management
  of the functions and performance of each part of the software becomes more and more complicated, and the requirements for the management ability of the project managers are also higher. Therefore, delivering the software as soon as possible can effectively reduce the management ability. Capability Risk.

• Information security risks
  With the growth of the software development cycle, the potential vulnerabilities in the software may also increase. At this time, if the important information of the customer data is included, it may be attacked by the scheming and spooky, resulting in losses. Therefore, delivery as early as possible can effectively reduce information security risks.

• Application technology risks
  The growth of software development cycle may be faced with the innovation of information technology, which will result in products having a competitive disadvantage to a certain extent. Therefore, delivering products as soon as possible can effectively avoid application technology risks.

• Quality control risk
  The growth of the software development cycle will inevitably make it more and more difficult to control the quality, because the software scale will continue to increase with the growth of the cycle, and the quality control of the software system will become more complex at this time. , requires the staff to be more mature in technology.

• Software design and development tools risk With
  the growth of the software development cycle, some defects and deficiencies in the initial design may appear, and the development scale may be different from the expected, resulting in the inability of the original development tools to adapt. Therefore, if the software can be shortened The development cycle can effectively avoid the risks of software design and development tools.

• Employee skill risk
  With the growth of the software development cycle, the scale of the software continues to increase, and the continuous development of software, in-depth testing and system analysis requires more and more employees' ability. If the employee's ability cannot meet the requirements, it may be Training or recruiting new capable employees is required, all of which increase the cost of software development.

• Human resources risk
  The software development cycle is growing, and employees at the early stage of development may leave for various reasons. At this time, problems such as code re-understanding and customer contact change are caused. At this time, the management of human resources is also more difficult and complicated. So delivering software as fast as possible can effectively circumvent this problem.

• Policy risk
  If the development cycle of the software is too long, the final software product may not be launched due to some policy reasons of the government. At this time, all the capital paid will be lost, which will cause a major impact. Therefore, the software should be delivered as early as possible. These accidents can be avoided.

• Market risk
  If the software development cycle is too long, the market's positioning of the current software product may change. At this time, the value of the currently developed software may be reduced. Therefore, delivering the software as early as possible can effectively adapt to the market to maximize its value.

• Marketing risk
  If the software development cycle is too long, the pressure on marketers will also increase significantly due to changes in market demand, because the competitiveness of software products may be slightly less than that of other competitors, and it will cost money to promote The more time and money you spend, the higher the cost, so delivering software early can effectively avoid these things from happening.