agile whiteboard

This is the second article in the agile development series. (One, two, three, four, five, six, seven, eight, nine) The so-called "no living" includes two meanings: not living in the law, not living in the air. The former is better understood, and the latter will be detailed in the next article. Instead of believing that there is the best way in the world, we must abide by it.Legal Statement The persistence of law is known as law enforcement. The typic

In order not to fall behind, I also began to learn scrum, today mainly on my recent reading of the relevant information, according to their own understanding, in their own words to describe the various aspects of scrum, the main purpose is two, one is to carry out the summary of knowledge, Another is that a lot of learning information on the Internet so that beginners are not easy to understand; So I decided to write a literacy blog, while also trying to share with the garden friends, hope to he

People who know how to share are the ones who get the most! 11 began to write a series of personal management in the blog Park, and later on other sites also wrote some, scattered in different network Places, in order to let everyone can focus on the agile personal related text, now most of the content has been moved to the Agile personal site. in the Agile perso

Agile development, no one will, no No documentation, fast activation, and users can change anything they say? The following is a joke, said Daniel of wangwu village- I recently switched to a job and earned 40 thousands or 50 thousands yuan after work. I took the drawing and saw it. Isn't it just a chimney? We are Agile teams. What documents do we need? Start working now! It was almost finished

In the previous three articles on the agile development of a background, is based on the author's personal experience as the main line to gradually understand the agile development from a personal point of view. Through the pair programming to complete the development framework of the building, in the framework of the fact that our formal agile process has not y

Agile methodologies have become the mainstream of current software development, and working code (and automated testing) is considered to be the most important output for the team. So is it no longer necessary to model it? Is the UML really dead? I don't think so. In this article, I will explore how the modeling approach still works and plays a key role in the agile era. Especially after the expansion of

Recently, due to the selection of Po, I had an in-depth discussion with VP in charge of agile promotion. I asked her a few questions in practice. She also replied patiently, and the details of the replies have reached the point where I was touched. I am very interested in the process and have thought about it as a professional process promoter. But I can't help but feel this VP, this operation requires great patience and confidence. Breaking old ideas

Agile Development Engineering Practice Project Management Iterative development Risk Value life cycle Multi-level project planning Full Team Daily Standing meeting Task Board Burndown Chart Demand management Demand Order Business Process Sketch Use case driven Development User Stories Architecture Evolving architecture Evolution of Design Component-based architecture de

Be happy, efficient, and balanced. Be a person who loves to learn, has goals, and understands the influence of life. From today until July 31, click http://t.cn/Rv3koHU to receive more than 1000 pages of "agile personal-Self-awareness, management self v0.8.pdf" for free Join us Training If you have learned about agile individuals and agree with the concepts a

From: Agile Software Development: Principles, models, and practices: Robert C. Martin, translated by Deng Hui] Agile Software Development Declaration:Individuals and interactionsBetterProcesses and toolsSoftware that can workBetterComprehensive documentationCustomer cooperationBetterContract negotiationRespond to changesBetterFollow plan(Although the right item also has value, the left item has greater valu

First, it is declared that this parallel development does not refer to parallel computing, but to some experiences and practices summarized by practical software engineering. Agile parallel development is a rapid development model that integrates software component technology and Platform + plug-in development technology. parallelism refers to the product's lifecycle, the project management process, Project R D process, and organization support pro

Document directory Analysis Model storming Design Model storming Why does this work? Adopting model storming Model storming is just in time (JIT) Modeling: You identify an issue which you need to resolve, you quickly grab a few team mates who can help you, the group names es the issue, and then everyone continues on as before. it usually common on agile projects, EXtreme programmers (xpers)Call it a stand-up design session or a custom

/ Leanthinking.pdf), it takes a lot of effort to hand over the document first, and then much of the information is lost during the handover, and there is always some new information added at each stage. All team members (PO, Dev, QA, Doc) sit together and use the whiteboard for face-to-head communication, saving time and effort and being effective. (See Alistair Cockburn, communication http://www.agilemodeling.com/essays/communication.htm in

This is the second article in the agile ecosystem series (One, Two, Three, Four, Five ). If there are still some factors that cannot be controlled by the Team in demand management that lead to implementation difficulties, there is no problem in the planning and tracking process? In fact, I have seen the entire group with the authority of Leadership (many of which are simply unable to handle the issue), but there are still many problems within the team

There are two common scenarios in the Agile manifesto that say "working software is better than detailed documentation" and it seems that the documentation is redundant in the work:1, complete a summary of the design, but the development process, this design is not enough to guide the programming work, it is better to directly ask PO to direct, communication between each other smooth. Finally this outline design becomes the decoration, no one looks.2,

1, Agile Test Quadrant-the division of labor in each quadrant? Who will do it specifically? When do you do it? 2, soap opera Test 3, exploratory testing 4, session-based testing 5, WATIR6, Fit Fitnesse8, to ility testing (reliability, interactivity, scalability) 9, agile testing in the automated test can keep up with the development of the iteration speed? 10, CruiseControl should be class is Jenkins/hudso

Waterfall development and agile development are the two most representative development models; Waterfall Development: Characteristics: 1. Emphasis on the document, the previous phase of the output is the next phase of input, the document is the only information at all stages of convergence; 2. There is no iterative and feedback, the waterfall model is not related to the feedback, so the change of customer demand is very not suitable; 3. Can be

Problem background Many activities in agile development involve full participation rather than personal involvement. Requirements analysis can also be a full participation of an activity. This reflects the agile development of "personal and interactive better than process and tool" values. Demand analysis is based on the understanding of requirements. Therefore, the full participation needs analysis helps

Agile results for personal work and life is mainly to cultivate result-oriented, planned, and targeted Manage personal time, regularly focus on some hot spots, efficient work, learning, and happy living habits! Three core elements: 1.3 rules (the rule of 3) 2. Monday goals, daily results, and Friday reviews (Monday vision, daily outcomes, and Friday reflection) 3. Hot Spots) The rule of 3 ): Three tasks are solved every day, three tasks are complete