agile whiteboard

development within a maximum of one week and deliver a pre-test ). After all the story in an iteration is developed, the testing group will perform a complete testing. During the entire testing process (pre-test, test), based on the daily build, the testing group will always take the latest compiled version number from the configuration library every day for testing, the developer can also change the problem ticket submitted by the Referer at any time and merge it into the configuration library

within one week at most ). After all story in an iteration is developed, the test group performs a complete test. During the entire test process (pre-test, test), based on the daily build, the test group will always take the latest compiled version from the configuration library every day for testing, developers can also modify the problem tickets submitted by testers at any time and integrate them into the configuration library.One feature of agile

an advance test (pre-test). When all the stories in an iteration have been developed, the test group then carries out a complete test. Throughout the test process (pre-test,test), based on the daily build, the test group is always taking the latest compiled version number from the configuration library on a daily basis, and the developer is also ready to change the questionnaire submitted by the Test personnel and fit into the configuration library.One of the characteristics of

1.Sprint Review Meeting: Not for the development team to do a successful "speech"---meeting does not necessarily have powerpoints pictures and documents, usually the meeting will not take more than 30 minutes of preparation time, but simply display the results of the work, all participants can ask questions and suggestions.2. After the Sprint review meeting, the development team will conduct a sprint review meeting. Some development teams skip this process, which is not appropriate because it is

One common feature of agile methodologies is that they point to "documentation", which argues that the traditional software engineering approach is too "heavy", called a "heavyweight" approach, and that the corresponding agile approach is a "lightweight" approach. It is because of the "lightweight" feeling that there is no power, not only can not effectively reflect flexibility, but it seems to be a methodo

responsibility, rather than money.. We all laughed at him in good faith and he was brainwashed by Mr. Ma. But in the White Paper, "company culture" is brainwashed, but brainwashed here is no longer a derogatory term. Then I asked Mr. W from thoughtworks, how did their company punish people? He said that with 360-level assessment, since their consultants are one project after another, 360 assessment takes place at the end of each project, however, the company will not punish a person for poor

often need to run and we don't want to come up with dormitory. Developers generally do not like meetings. Therefore, I will meet the customer twice a week to discuss the progress and various situations, and may adjust the download work plan when I come back.Responding to changes is better than following the plan Although this is a benefit of agile development, who would like to hear the word "change? Who makes the mistake that requires "change? A com

the plan, prepares adequately, the other person listens and questions.3. Remove any information system and use the whiteboard.4. Please extend the review cycle, not too frequent, really miserable.5. If you do not have a flat, bureaucratic tendency, then don't be agile, in other ways.6. There are many types of meetings in agile, and meetings are not for programme

save my username and password locally so that I can log on automatically.9. As a registered user, the user name and password I want to save locally are encrypted so that my automatic login information is secure.10. As an anonymous user, I want to directly access services with anonymous permissions so that I can quickly use the services provided by the system. Send representatives to each group to post and describe the splitting results of the group.Please comment on each group.Record the com

1,leangooLeangoo is great for scrum and agile development, and we can use it to easily create sprints, add user story cards or task cards, add estimated story points to user stories, or drag and drop to move cards to different status lists. You can also quickly schedule tasks for a team member by dragging it onto a task card.As a free, concise, visual and Agile Team collaboration tool, its simple experience

Last empire-dilemmas of agile companies (2) This article is excerpted from agile invincible In the next few days, A Jie waited with confidence for the call from agile. When Yuan Lang informed him to get an offer, he imagined what he wrote and painted on the whiteboard next to his seat. A week later, but I still don't h

Ext.: http://www.cnblogs.com/fnng/archive/2013/02/03/2891246.htmlQuick and sensitive reaction.In the field of agile software development, more attention is focused on people as the core, iterative, progressive development method. Compared to traditional development methods, this method can be developed faster, on-line, feedback, adjustment, iteration. To develop products in an agile posture.The difference b

with customers two times a week, discuss progress various situations, come back may adjust the download work plan. Responding to change is better than following plan Although this is the benefit of agile development, who wants to hear the word "change". Need to "change", who is wrong. A complete development, is a war, bang, and then decline, three and exhausted. So the response to change, can only come out of my link now. Before the development of t

The first article in this series, "User story-driven agile development –1." Planning chapter "To share with you how to use user stories to help teams create requirements, in this article, we look at how to use these user stories and feature points to form a product backlog." A product backlog is a tool that is used in agile development to manage requirements lists, prioritize, form iteration plans, and orga

The 14th chapter uses UMLBefore exploring the details of UML, we should first talk about when and why to use it. The misuse and misuse of UML has caused too much harm to the software project.14.1 Why ModelingModeling is to figure out whether something is feasible. When models are much cheaper than real entities to build, we use models to study designs.14.1.1 Why build a software modelUML is used when we have some definite things to test, and using UML is less expensive than testing with code. Fo

feeling that the meeting gave her. There were only four words: A knife, a sword, and a shadow! All participants will participate in the conference to express their own opinions and strive for the success of the project. That's all we need! Author: Zhang chuanbo Www.umlonline.org Please specify the above content for reprinting; otherwise, please do not repost it. Is the daily meeting held like this? Extreme Programming has daily standing meetings and scrum has daily morning meeting

Masters should not only sum up some theories about agile methods, but also have practical methods to operate and cooperate with the corresponding business models. Otherwise, they will always say that agile declarations are principles, practices, or experiences, there is no theoretical or business model support, and there is nothing to talk about when it comes to charging problems. Who pays for

Recently, I organized my previous scrum documents into a document. In the following team and project development, I introduced some practices of scrum according to the project, improve the collaboration capability and project delivery quality among team members. 　　References: Easy scrum journey-agile development story and agile invincible Scrum and XP in smoke Martian

defect tracking, customer service, demand collection, process approval, task tracking, project tracking, and agile management.3. Axosoft OnTime ScrumAxosoft OnTime scrum helps development teams manage to-do, product launches, and simulate project sprints. This HTML5-based tool provides the ability to create charts and manage dashboards, which can track code features and fix bugs as you walk through the work hours. In addition, HTML5 is part of the Ax

Part III Agile Test Quadrant6. Purpose of the testQuadrant for Agile TestingSupport Team Testing : helping to develop and develop productsQuadrant one: tdd/td test. Use and apply the same encoding. The general internal quality is defined by the programmer and participates in the test. CI environment.Quadrant Two: Test the details of each product, and the automated test runs on the business logic layer. Auto