update for sprint

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14 Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim Sprint Cyc

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

design, including login registration interface, product information interface, user feedback interface and so on, it takes about 30 hours of working timeGroup Chen Zhili: Background management, including the establishment and connection of the database, the update of the quantity of goods, it takes about 20 hoursGroup One: Further market research and user demand analysis, takes about 15 hours of timeCrew Zhao Yonghen: Software Testing and maintenance

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

A Sprint plan meeting is held on the first day of the sprint. This meeting is divided into two parts. Plan meeting 1 is attended by Po, Sm, and team, it is mainly to select the established product backlog that needs to be placed under the current sprint from the product backlog, and then the SM and team participate in the planning meeting 2, split the story of th

Introduced: For Agile Software Development, it is important to keep track of the progress of the project at all times, as you can keep abreast of the health of the team and deal with unexpected situations in a timely manner to ensure that our projects are delivered on time after each iteration. Implementation mode: The best tool to see the project progress is of course Burndown chart, we use Jira to do project management tools, Jira has a view of the show, can very intuitive display story bur

The Sprint planning meeting was held on the first day of the sprint, and the meeting was divided into two parts, with the Plan meeting 1 being attended by PO, SM and team, mainly from the product backlog to select the backlog of products that need to be placed in the current sprint, and then by SM, Team participated in the program meeting 2, the story of the back

Time Date Place Job 18:40 5.21 Nine real Integrated Network Assistant! 6:49 5.22 ~ Change Solution Integration! Difficulties encountered: Last night, the integration of the pie failed, many of the problems were never thought before. Think that the class are added to the new project, the Lib package is directed in, draw a new interface with the original ID value, and then build on the line. This morning can only

part of the sixth assignment according to the progress of the project Learn the UML Diagram and the building method to learn about the tools required for blogging and design. problems encountered: a database field with a length exceeding the limit error causes an insert exception, and some hidden bugs require multiple tests to discover. When you join a group, the request fails, and there is no error returning information that needs to be parsed from the logical layer of the code.

Complete and publish Summary blog, sixth chapter of building Law, learning UML diagram Wu Jingan Unit testing of completed functions Improve the test results of completed functions, design test cases for the function of the next step plan implementation of the meeting Hu Zhiquan Complete part of the sixth assignment according to the progress of the project Learn UML diagrams, Learn the tools your blog and design requires. problems

In the agile development framework of scrum, the most important part is the Sprint plan meeting. If the meeting fails, the whole sprint will make the scrum team suffer and it is difficult to complete the initial sprint goal. After several attempts, we finally found our own model. These methods and principles are the best for us. Based on our own knowledge and our

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future. This article mainly aims to check your understanding and usage of the scrum Sprint plan meeting, Through this article, you can check1. process and steps of your scrum Sprint plan MEETING2. output results of the MeetingSprint

The Software engineering Sprint = Let us realize a lot of places, do not know how to arrange a reasonable time, a lot of things are more procrastination, casually in the past, a bug may be a few days to solve, but also may be left behind. Because our team members are relatively busy, the class committee has three, especially the monitor, usually a pile of work, it is difficult to have time to come out to the meeting. There are also some of my delay di

1. Scrum plan MEETING Before each sprint starts, you need to hold a Sprint plan meeting. The meeting time is generally 4 ~ 8 hours, participants include product owners, scrum masters, scrum teams, and others of interest, such as managers and customer representatives.The product owner selects high-priority tasks from the product backlog and works with the scrum team to determine how many features are requi

The Sprint Review Conference has long been an important part of scrum, a mechanism for the team to get feedback on the product increments that are delivered by the iteration. At the Sprint review meeting, the product owner determines the priority of the next sprint's requirements based on the feedback received.So, is the sprint review now obsolete?Ten years ago,

For more than a year, we've been using Ibm®rational team concert™ to support our Scrum teams, enjoy its features, coexist with its shortcomings, and develop its next version. Using the IBM Rational Team concert V2,jazz and the Rational Group concert teams can make significant improvements to Scrum and agile assessment, planning support delivery (not to mention more improved WEB clients and many other new features). Sprint Planning As we have used IB

In my previous introduction, I described the relationship between release, sprint, and story. Reference: several meetings in scrum management and our practices To put it simply, a release can include several sprints, and a sprint contains several story. Of course, a story can span multiple sprints or release. But what about the version? In practice, we need to use the GIT tag pairCodeTo ensure that all th