scaling agile methods

scrum is a development process that allows you to see your team work efficiently.Three major roles in the scrum development processProduct Owner ( Product Owner )Responsible for determining the function of the product and meeting the required standards, specifying the release date and delivery content of the software, as well as the right to accept or reject the development team's work results.Process Manager ( Scrum Master )Primarily responsible for the smooth implementation and execution of t

1. Write a story This chapter only lists the characteristics of good stories. Invest: Independent, negotiable, valuable to users, evaluable by developers, small, and testable. 2. User Role Modeling This chapter only lists how to obtain a user role, but does not provide a good basis for the Division. The specific method is a refined process. Brainstorm to find all possible roles Sort and check the relevance Merge and remove related roles Abstract user roles. In addition, this chapter provi

(test-driven development).When you encounter problems, you must promptly find the relevant personnel to communicate. However, there is a problem, if the developer is developing, be disturbed may be decided very uncomfortable, in order to ensure the effectiveness of communication, you can:1. If it is not very urgent, you can wait for the relevant staff to communicate when the rest of the time.2. Solve a problem, first comb the emotions, then comb the relationship, and finally the problem itself.

keep the story: Preserving the story is more valuable for subsequent maintenance of the product and the need for some documentation after the project is over.In a word, the advantages of user stories make them stand out in many demand methods, and there are shortcomings, which require some extra cost to compensate; User stories are easy to understand, but they are not easy to use, so be aware of the various symptoms that may occur during the iteratio

Agile Development (Development) takes the user's needs into the core, and uses iterative and step-up methods to develop software. In agile development, software projects are cut into multiple sub-projects in the early stages of construction, and the results of each sub-project are tested for visual, integrated, and operational use features. In other words, a lar

. Iterative refers to continuous improvement, in the iteration, the software can be gradually improved; promotion refers to the team to develop and release software according to the function point, which can make the project steady progress, reduce the chance of rework. Projects that implement the scrum process often iterate over a period of 30 days, a process known as sprint. ScrumMaster is the equivalent of a traditional project manager, but more like a leader and organizer, he has a closer re

iterative and incremental process that iterates every 30 days and becomes a sprint.The product backlog is a list of functional requirements to be developed. Sprintbacklog is a list of tasks that a team commits to complete in the current sprint.16th Chapter: Other topicsTools for using the right projects and teams.Iterative processes can lead to repeated changes in the user interface.Once the story is complete, tearing away the story card will have some fun.Part IV A complete exampleThis section

Php image cropping and scaling methods /* Check whether the original file exists and obtain the information of the original file */ $ Org_info = @ getimagesize ($ img ); $ Img_org = $ this-> img_resource ($ img, $ org_info [2]); /* Size ratio of the original image and thumbnail */ $ Scale_org = $ org_info [0]/$ org_info [1]; /* Only when the width an

, easy to cause the story is not clear, and life is a factor of influence, use case is a permanent "artifact". Finally, the scenario is a detailed description of the user's interaction with the calculation. It is larger and more comprehensive than the use case scenario, and the difference between the story is the scope and the details.It is also important to note the following: No matter how comprehensive the initial assumptions are, we cannot fully define a complete system with considerable sca

Use of iOS UIScrollView proxy and several methods of listening in the scaling age There must be at least three steps: I. Implementation Protocol 2. Establish relationships 3. Set the scaling range For details, see the code: # Import "ViewController. h" @ interface ViewController () // Comply with this Protocol First @ property (weak, nonatomic) IBOutlet UIS

. Measuring and monitoring dataThe actual number of hours spent completing a task or story has no effect on the rate of the secondary. The Daily Burndown chart is useful in iterations, and it shows the number of hours remaining per day in the iteration. Designing and testing a graph of the number of defects that occur on an average per story point can help us find out whether the increase in team rate is at the expense of quality. Developer responsibilities try to do the next story after complet

There must be at least three steps:One, the implementation of the ProtocolSecond, establish a relationshipThree, set the range of the zoomSee the code for details:#import "ViewController.h" @interface Viewcontroller () The use of IOS Uiscrollview Agent and several methods of agent monitoring during scaling

The use of iOS UIScrollView proxy and several methods of listening in the scaling age, iosuiscrollview There must be at least three steps: I. Implementation Protocol 2. Establish relationships 3. Set the scaling range For details, see the code: # Import "ViewController. h "@ interface ViewController ()