agile whiteboard

phenomena, but also understand the essence ." Q: questioning: "What do you see? How do you feel ?" R is called spectives (Review): "What have we learned? What will we stick? What should be new ?" S is sensitive: "I'm wondering if they're ready ......" T is transparency (transparent): "I hope you can try it like this, because I think it will help you ......" U (unlock): "I didn't expect this team to do this !" V is vocabulary (Word): "yagni? Burn up? Muda ?" W is welcoming (a

The origins of Agile developmentIn the late 90, the traditional way of software development because of its complicated process, as well as the strict requirements of the document, resulting in a large degree of efficiency decline, which is what people call "heavy crisis." For this reason, people begin to reflect on the pros and cons of traditional methods, and improve their drawbacks, and propose an agile a

Creating useful software is the door process. This is not a black-white formula for success. However, there are some agile engineering practices, practice has proved that it has repeatedly added value to the enterprise, but the premise is to be considered before use. In this article, I'll share with you 5 specific ways in which your organization can benefit from agile engineering practices. (Assuming we us

Good project communication is the foundation of project team management and an important embodiment of the management effect in Agile Project Teams. The communication effect is good and everyone is happy. The project is not only progressing fast, but the quality is still good, otherwise, vice versa. Table 1. semantic tiveness of communication strategies on agile development teams. Communication

12 principles of agile development (Here we focus on principles 4-6 ): Criterion 4: Business people and developers must work together daily throughout the project. Translation: business personnel and developers should work together in the project development process. Note: The customer participates in the project from the very beginning, which means that the development team can accurately understand the user's needs and make timely adjustments based

Rugby and software development (8)This article is excerpted from agile and invincibleBook All bookstores are on sale Everything at the Palo Alto went exceptionally well.Charles only mentioned the candidate as the project manager candidate, so there was almost no pressure on the Project Manager during interview. After warm up answered the question of the year in which he joined agile and what kind of positi

ArticleDirectory 3. No principles "Agile individual", this is unknown at first, but once heard of it, I will like the synonym for personal growth. It has now evolved from fragmented sharing two years ago to a systematic growth system. Many of my friends have helped me to promote it to people around me. I feel more responsible for promoting "agile individuals" and helping more people start th

tests define the details of each story and are a decisive basis for judging how the story behaves correctly.3.5 Mission PlanningAt the beginning of a new iteration, developers and customers are co-customizing the plan. The developer breaks down the story into a development task. A task is a feature that developers can implement within 4-16 hours. The developers analyzed the stories with the help of the customer and enumerated all the tasks as much as possible.These tasks can be listed on Flipch

decisive basis for judging how the story behaves correctly.3.5 Mission PlanningAt the beginning of a new iteration, developers and customers are co-customizing the plan. The developer breaks down the story into a development task. A task is a feature that developers can implement within 4-16 hours. The developers analyzed the stories with the help of the customer and enumerated all the tasks as much as possible.These tasks can be listed on Flipchart, Whiteb