scrum organization

Beta stage Seventh Scrum meetingSituation Brief Beta stage Seventh Scrum meeting Agile development start time 2016/12/20 00:00 End time for Agile development 2016/12/21 00:00 Summary of basic content of the meeting Deadline near Participate in the discussion staff All participation

Job description Fu Mei XiaoThe work done yesterday1.Daily Scrum, daily meetings and daily assignments and checking.2. Modify the properties of the database tables as requested by the second panel.Work today1.Daily Scrum, daily meetings and daily assignments and checking.2. Code review of the thread pool, exception handler.The difficulties encounteredSince the interface for the exception processor has

Scrum swept to our department. Reality: 1. A new concept and short-term training for current departments2. There is no push at a higher level3. a scrum team composed of several members of different functional teams.4. Some people have not even attended scrum Training This is a controversial afternoon, with controversial Planning Meeting:1. "Why are there so m

The 3 artifacts of scrum include: Product Blacklog, Sprint Backlog, completion criteria.1. Product to-do List (products Blacklog)Product Blacklog is the core artifact in scrum, which is a functional description of the entire product, all functional descriptions are ordered, and the team works in a prioritized order.It is the only source of product requirements, and all the work of the development team comes

During the sprint, we will communicate through the Standing Meeting every day. Below I will list the main contents of the meeting. (The following meeting content is from scrum checklists) Meeting content Target Communication and coordination of work progress among team members Meeting preparation Participants: all members of the team,Scrum master,Product owner (optional) and related personnel (

As the agile VP came to China, kanban became a hot topic in this discussion. Many teams are using dashboards to replace previous scrum. Kanban originated from Toyota and is a classic representative of the Toyota generation model. Almost every company studying Toyota TPS unconsciously regards Kanban as the first model to be introduced because it is intuitive and effective. Agile visualization is a very important element and naturally comes to mind the

According to the first chapter of scrum in action, we can see several meetings below.Release Planning The product owner is responsible for the release planning meeting. The goal of this meeting is to specify a product development cycle consisting of several release, each of which must specify the delivery schedule. For example, there should be a release plan similar to the following table at the end of the meeting: Some procedures and methods are req

Label: style blog http sp strong file on problem log Scrum meeting Report Key points: Discuss the existing and functions to be implemented in the xueba System Short-term task allocation Preliminarily determine the tasks of the team members in the first round of iterative development I. Completion of existing and implemented functional projects in the xueba system: User Information Management: Registration (email), logon, logo

Today, I received the extremeprogramming API@ Yahoogroups.com): "The benefits of automated building and continuous integration are required so that their VP can take a while to optimize their build scripts, in order to shorten the time from 3 to 4 days to 12 hours. Because their unit tests run for too long and building often fails due to unit test failures ." This is not ridiculous, because it is common in many companies, but when it happens to a software company that claims to be "agile" and bu

Robert Sabourin shared his test practices in the scrum team in the out of the frying-real-world stories of scrum migration-and no one got badly burned article. Traditional tests are probably divided into two types of positioning: (1) "goalkeeper": Quality champion, blocking the release of unreliable, ineffective, and bug-filled versions. (2) "information provider": provides a large number of positive inform

One of the most important systems in scrum of agile processes daily standing meetingWhat to know:Question: Why not use the email report instead of the daily meeting?e-Mail can not replace the daily meeting, e-mail will only increase the cost of communication, and can not provide details or give others the opportunity to ask questions, nor can help other members to solve the problem.Purpose of the Standing meeting:1. Let everyone know what other people

This article was 2:51:42 2016/12/8 Republish to Buaa_overwatchBeta Phase Second Scrum meetingSituation Brief Beta Phase Second Scrum meeting Agile development Start Time 2016/12/7 24:00 Agile Development End Time 2016/12/10 00:00 Summary of basic content of the meeting Determine the basic tasks for the next we

In scrum, The Sprint plan meeting is the most important event, and the second important event is the review meeting, because this is the best time for the team to make improvements. If you do not review it, you will find that the team is making the same mistake again. After the sprint review meeting, the team needs to hold a review meeting. I will list the main content of the meeting below. (The following meetings are from

This series records the thinking methods and class design processes of Basic Library Development in actual work. Additionally, we will also mention how to use similar scrum processes in practice to organize your work and how to use TDD in such work. This world is filled with something called dbhelper. Microsoft's entlib has been constantly updated for many years and the world has been able to find all kinds of dbhelper classes released by unknown pe

It was written by Swedish scrum experts. It is very vivid and has a very practical significance. It is easy to read and complete in a day or two, It is recommended to read. The following is a summary of some highlights (of course, a lot of highlights are in the mind, not to write) 1. the user stories in the product backlog generally include the following fields: ID Name: Importance level: Give a score with a differentiation interval, such as 10,

Tags: Agile development scrum test-driven development Pair Programming agile coach The word agile and agile development is very popular recently! Agile development is the ability to quickly develop software when demand changes rapidly. The terms most relevant to agility are: Extreme Programming (XP), Pair programming, and test-driven development (TDD. Agile modeling (AM) includes four XP values: communication, simplicity, feedback, and courage. In a

Team name, team goal, team slogan, team photo;Role AssignmentProduct Owner: Determine the development content and prioritization, maximize the value of product and development team work.Scrum Master: Responsible for ensuring that the team follows the theories, practices, and rules of Scrum. Scrum Master is a service leader in the team.PM Project Manager: Team leader, lead, balance, drive, motivate, target,

hard; Daily scrum has some of the absence of members, for everyone sync up progress has some impact; PM did not change the status of work item in TFS in time (so this time the burndown figure looks so uncomfortable); PM Update blog is not timely, it should be daily scrum in time to update the progress of the day, the actual update frequency into two days a more. In the following Sprint 3 a

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

Recently, I have been reading "Gold Mine", a book about lean, which tells about various Kanban and process sorting. I can't help but think of some scrum processes, A lot of Knowledge gives me more thoughts. The process in lean is based on Kanban to pull the production at the front. At the same time, it controls the production cycle and pace at the front to ensure the reduction of In-process products, thus reducing the inventory in production, it also