The experience of reading this book is agile, even if you do not understand srcum ** and other methods, as long as you stick to your values and make improvements in one direction, even if you cannot "have code that meets the release requirements at any time", today is better than yesterday and it is successful.
Determine development goals through business analysisThere must be a problem in how to be agile. You can perform self-check on the business status (cost and time resources) and Strategic Objectives (value proposition ).
The business, which is not the core value proposition but the most costly, is the goal of improvement.
Architecture importanceA good architecture will adapt to changes and ease of maintenance, greatly improving the development and maintenance efficiency. The architecture guardian is responsible for the evolution and maintenance of the architecture.
Starting from continuous integration and Quality SystemContinuous integration ensures the stability of the main version better than single integration.
Automated hierarchical testing applies different test scenarios at different levels and effectively balances resources. The automatic release pipeline ensures that all codes meeting the release requirements are available at any time.
Use the right tools to increase productivityPublic development environment
Develop scalable testing frameworks for real-time measurement and tracking (instead of using measurement to manage, but using measurement to discover improvement points) developed tools and methods
Allow participants to define agile/lean practices
Team flexibility rather than operation
Agility must adapt to the actual business environment in the process of implementation, and the form may change. The only thing that remains unchanged is the value.
From Weizhi note (wiz)
Attachment List
HP large-scale agile development practices
