Agile sprint planner

Guide to the complete use of the agility sprinter

Preparing for Sprinting: Sprinting name #sprintNameDate of commencement, target #sprintGoal； (a) A list of members to maintain the availability/capacity; HistoryVelability List and Simple Charts; To-do story backlog contains the number of points. (a) Statistical display of capacity, planned, average speed, number of days of sprinting; Capacity Bar #capacityBar Whether the hint is over. Data are stored locally and can be exported for planning, sharing, clearing. Theme is stored in theire. The Scrum program will be screen-screened, not a Jira substitute, and will not automatically pull stories from Git.

Modules and Functions

• Members:addMember/updateMember/delMember/renderMembers。
• Rate:addVelocity/updateVelocity/delVelocity/renderChart。
• Story:addStory/updateStory/delStory/renderStories。
• updateStats Summary of data/planned/development/days;saveState/loadState Enduring.
• exportPlan/sharePlan/clearAll Distribution and clearing.

Plan the process

1. Write a sentence on the target, set a date range.
2. Available capacity of members (leave to be deducted).
3. Filling in the last few rounds of Velocity for reference and avoiding head-to-head stories.
4. Draws the story from the backlog, the total points are close but not significantly above the capacity.
5. Export/share to team to build a Spring board in a formal tool after the meeting.

Border

• No dependent sorting, no automatic demolitions, no burn-out map real-time data source.
• Points are relative estimates and are not human-capable converters.
• Sharing links may contain targets and story names, and be sensitive.
• The volume bars are a reminder, and overload is still allowed to be preserved - discipline is on the team.

FAQ

- Re-engineered plans?

Recovers (based on Savestate).

And milestones/WBS relationships?

WBS Dismantling Structure, Milestones Looking at Nodes, Page Sprinting Capacity and Story Commitments.

How do you fill that out?

Fill out the actual completion points of past sprints for forecasting purposes, not nuclear weapons tests.

What if we overdo it?

Cutting range or down priority rather than working late to fill pits.

Disciplinary recommendations

(b) Planning time boxes; Story INVEST; Targets can be tested. Public computers are empty. The subject switch does not affect data. The end-of-the-cycle tool is improved when it is aligned with the timer for station accounting.

Capacity and story discipline

(a) Members ' capacity to take leave and fixed meetings; The story points are derived from a relative estimate of the meeting. Velocity takes the last three rounds of medium to more stable. Overtime cut-off rather than acquiescence to overtime. The export of the plan is annexed to the proceedings.

Sharing and clearing the field

Share links with simultaneous snapshots, and be aware of the dissensitization of the story. Clear as ever. Plan-implementation-improvement of closed loops with RACI, station meeting, review tool. The theme does not affect operational data.

Local data and use boundaries

The draft and the results of this page are mainly stored in the current browser environment, site data are cleared, equipment is replaced or privacy patterns may lead to loss, and important working hours, sprinting, RACI, contract and stamp configuration are requested to be exported or amputated in a timely manner. Once the public computer is in use, sensitive information should be emptied. The tools are used to enhance efficiency and are not a substitute for formal personnel attendance, project management, key hosting, legal services or property contracts, depending on the organizational system and local regulations.

Plan will be a screenshot.

First, the target and date, then the volume bar and Velocity, and then the number and owner, one by one. The controversy is either small or moved to the next round. The statistical area is close to capacity and can be closed. Export plans to post minutes of meetings and share links to absent colleagues. Local status refreshs to recover, and it is still recommended that double backup be exported.

The station will be retraced.

Control the daily synchronization at the time of accounting for the service station for the performance period; Ends the collection of improvements using the retrospective tool and reflects the quality of the next volume and story. This page does not follow the daily checkout, and the completion is on the panel system. Public computer clearAll.