agile whiteboard

Agile basic knowledge----demand management based on story (I.) Demand management based on story (1) Using story mode to manage requirements, the large MRD is divided into a suitable granularity, and can be independently delivered story (usually each story can be completed within 1-5 days, including design, development, testing), the requirements are clear, easy to reach agreement, and can save a lot of requirements review time. (2) require PM to be

# Practice group # register with the second batch of agile individual promoters Note: group activitiesDeadlineBy March 2014March, Members of the first and second batch of PromotersThe annual fee ends here. If you join in any month in the future, you will only pay the annual fee until January 1, February 2014..2014Whether to continue the group activities or other forms to be determined after March. Registration address: http://www.minjiegeren.cn/ho

Agile basic knowledge----demand management based on story (II.) (1) Periodical release Regular release of the line, the whole project divided into iterations, each iteration time size fixed (basic fixed), the end of the iteration on line delivery. (2) Iterative planning Iterative planning is the equivalent of a plan for the entire iteration, helping us manage and guarantee delivery for each iteration. A. Prerequisites for iterative planning:

the software reaches a certain scale, different user stories cannot be simply arranged as list structures, but rather to establish dependencies so that they can be displayed at different levels, and in addition to enhancements, refactoring, and defects, these user stories should be subordinate to certain business data or business operations, and their syntax cannot be used as ... ... OK...... In order to ... ", but to study its special grammar. content of this issue: 1. Review of Phases 1 and

Agile basic knowledge based on story----iterative initiation and iterative review In addition to the need to explain the accident, there are only two meetings that require all team members to participate, namely, "Iteration Initiation" and "Iteration review." (1) Iteration Initiation will Before the iteration begins, an iterative launch will be convened for the following two purposes: Clear iterative cycle, that is, on-line time; Identify the ite

updated? B) further details and decomposition can be considered if you need to ask for the reason for your work that has been suspended for more than two days. C. Encourage exchanges at regular meetings to gradually form an atmosphere of communication. 3. All work and progress are displayed on the whiteboard or wiki for unified management. A) The initial job description can be simple, but verbal consensus should be formed at the planning and summary

an environment and atmosphere that attracts developers is one thing that managers of all companies should consider. The departure of a core product developer may paralyze the current project or order, which has become a major concern affecting the survival of many small and medium enterprises. My company is not only famous for its agile process, but also attracts a large number of high-level developers with its unique culture and team atmosphere. The

? What about check-in that is not related to user stories? Merging code is a hassle, so I want to do as little as possible! I have more questions! Reference Resources Downloadable PDF IntroducedThis article describes an example of how to work with multiple teams in an Agile environment for version control. I assume that you are familiar with the basic elements of Scrum, XP methods, and taskpad. These methods are not in

managers of all companies should consider. The departure of a core product developer may paralyze the current project or order, which has become a major concern affecting the survival of many small and medium enterprises. My company is not only famous for its agile process, but also attracts a large number of high-level developers with its unique culture and team atmosphere. They not only agree with agility, but also look forward to this air of equal

the internet age. At the end of 2014, he was determined to be a Lightweight team agile collaboration Tool . six months later, Leangoo was born. because there are many years of user accumulation in the Scrum Chinese network, Leangoo online more than half a year to get 100,000 of users. These users constitute both the Internet startups and some traditional transformation enterprises. Compared to the 2 major pain points of the traditional project manage

the internet age. At the end of 2014, he was determined to be a Lightweight team agile collaboration Tool . six months later, Leangoo was born. because there are many years of user accumulation in the Scrum Chinese network, Leangoo online more than half a year to get 100,000 of users. These users constitute both the Internet startups and some traditional transformation enterprises. Compared to the 2 major pain points of the traditional project manage

Ext.: http://blog.csdn.net/kerryzhu/article/details/8812589Today, we also discuss such an old topic, do you feel the same? Because Mr. Dening, who was Google's China Test manager two years ago (at the end of 2010), wrote an article on "What is Agile Software Testing" (published on the INFOQ website [1]), which has already been discussed, "Agile software testing is more of a concept than a process." [2] In 2

developmentIt's too much for the team !"Azi looked forward to his face and said, "I suggest you look for a set at the end of each sprint .""No problem! I have a dish in my house! Back to today's theme, Let's name the first sprint the big con !)". A Jie wrote "sprint1-the big con!" on the whiteboard !)"."In fact, this also shows our situation! The first time we adopted scrum, we were very much looking forward to this scrum process. At the same time, w

that this method has achieved better results. Maintain the status bar. To make the progress of iterative development clearer to leaders. We will paste the completion stories of each iteration plan, the tasks to be divided into, and the statuses of the stories and tasks on a whiteboard. On a daily basis, the agile team members will hold a stand-up meeting, review the work done in the previous workday, the

. Each story can be considered as an independent feature. Each story should be able to complete development and deliver pre-test 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

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