Agile Implementation of Project C (3)-5 iterations

Time flies, and in a twinkling of an eye, Project C has come to the fifth iteration. In the fifth iteration, what is the situation of the C Project? The answer is that it is still a stumbling block.

For many people, the results of such agile implementation are unacceptable. after such a long period of implementation, they are still stumbling. Implementation agility looks like a movement. People always expect the end time of implementation agility, but this is agile and practical agility. (Agility is not only a marathon, but also never ends .)

I remember my previous lectures on scrum. One of the three pillars of agility is transparency. It means that Agility does not solve the problem itself. It can expose the problem continuously during the implementation process. The agile community has an image ".

The solution depends on the organization itself. However, for most organizations, they are not prepared to constantly face and solve the problem. Implementing agile or even failed is unexpected.

Current Status

When the fifth iteration was halfway through, the project team began to report bad news. Because the API cannot be provided in a timely manner, it is estimated that it is difficult to achieve the development goal of this iteration.

Progress

Objectively speaking, the project team has made great progress in the five iterations.

1. Basic team formation

In the past, due to the meticulous division of labor and the waterfall process, at the beginning of the formation of the team, it was basically a battle for everyone. Do not voluntarily expose information, and wait for tasks and coordination to be highlighted.

Now, the entire team is united under an accurate goal, and we need to deliver the iteration goal. Under this common goal, internal coordination becomes easier and personnel are more proactive.

1. The workflow starts smoothly and a basic integration environment is established.

Under the pressure of iterative delivery, the team quickly formed and got used to the workflow.

Teams are divided into development teams and demand teams. All jobs are listed on the whiteboard and collected by team members. The Development Team is responsible for developing and testing the release based on feature/bug, forming a rapid development process. The demand team is responsible for external demand coordination and demand refinement to form a list of feature to be developed by the development team in the next iteration.

1. Basic Technical Skills

After several iterations, the Team has basically mastered the technologies required by the work through peer programming, unit testing, and other practices.

1. Continuous delivery of results

Despite all the pitfalls, each iteration of the team is continuously delivering results that meet quality standards. Unfortunately, no iteration is in line with the delivery of the iteration target.

Current Difficulties

Previously, the team had solved most of the problems affecting work. So what are the current difficulties that make the team difficult? It is also very easy to say, that is, the API problem.

The API that the team relies on comes from an architect in the United States. The architect shares resources with multiple teams. However, the architect and the team have different priorities and there is no work commitment. This leads to frequent waiting for the team, which is only occasionally paid attention to by superiors.