Agile is a development method for the software development process, it will guide us to complete the project step by step. Agile is really about the project moving into substantial development iterations, where users can quickly see a base version of the product. Agile focuses on rapid market responsiveness and high upfront customer satisfaction. In Forbes’s article, it emphasizes that the teams should focus on satisfying the customer. They are also focused on maximizing shareholder value. But an overemphasis on shareholder value and efficiency often leads to a quality problem, and this efficiency is based on sacrificing planning time. Agile often does not have enough time to complete the empathy step of design thinking.
In Agile, the number of project teams should not be too large. Likewise, in Scrum, the number of people is also limited to 5-10.
There is a high-risk in Agile implementation. Under the absence of proper detailed planning, team members need to communicate in real-time to ensure that their work is connected. And any miscommunication may cause work off from the track. It is very similar to Scrum in this respect, In Scrum, task assignment is a team responsibility, so each member should maintain a constant awareness of the status of the project.
In Agile, requirements change much more frequently than in design thinking. In Agile development, some requirements or problems are unknown early in development, or even do not exist at all. So in Agile development, the early stages of development may not define a problem. During the development process, after one Sprint after another, the problems and customers needs became more and more clear in real-time.
I found the concept of Sprint to be a very worthwhile one, as we had to take one iteration of development and get it done as fast as possible. This means releasing prototypes that implement basic functionality in a short period of time. Then collecting customer feedback, and changing the product development requirements in real time based on that feedback. Changes in Agile should be based on customer satisfaction.