Scrum Agile Project Management essentials

1.
Brief introduction:
Agile project Management in our country started relatively late, the successful use of a few projects
65% of Agile Project users are scrum

2, the characteristics of the Internet era, lei June words:
Focus, extreme, word of mouth, fast (Agile project development is to be fast)

3, agile development of the various portals

　　

4. Four manifesto of agility and its connotation
1) Individuals and interactions above processes and tools
2) Working software is more than detailed documentation
3) Customer cooperation is higher than contract negotiation: emphasizing cooperation with customers and using less contract to speak
4) response change is higher than the following plan: Fast response to customer requirements, do not need to fully develop the software to enter the market, you can develop certain functions, put into the customer, and then continue to improve

5.12 Principles of Agility
1) The most important thing for us is to meet the needs of our customers by delivering valuable software early and continuously.
2) We welcome changes in demand, even in the final stages of development
3) Recurrent will be able to work with the software, the delivery interval can be from a few weeks to months, tend to adopt a shorter cycle.
4) throughout the development of the project, business people and developers must work together every day.
5) Be good at motivating project personnel, give them the necessary environment and support, and believe they can complete the task. Focus on motivation
6) The most effective way to communicate, both within and between teams, is to speak face to head.
7) The software available is the primary criterion for measuring progress.
8) Agile processes promote sustainable development. Funders, developers, and users should be able to maintain a long-term, constant pace of development. Traditional (early stage loose late)
9) The improvement of technology and the continuous improvement of design will enhance agility.
10) to be concise, that is, as large as possible to reduce unnecessary work, this is an art.
11) The best architectures, requirements and designs are derived from the self-organizing team.
12) The team should periodically reflect on how it can be more effective and adjust its behavior accordingly. Study, summarize, reflect

6. Scrum Project management process

7. Role:
Product Owner: Determine which features first go to the sprint to-do list, accept and reject the work of the development team, and determine when to submit what features at the user and customer's point of view
Scrum Master: Team leader to solve the obstacles in team development,
Development team: Requirements analysts, designers, architects, programmers, etc.

8. Essence
1) Small steps forward, continuous optimization: Not the pursuit of a step to step, the pursuit of continuous accumulation of functions
2) Continuous delivery, iterative development: The work we do is visible to our customers at the fastest speed, allowing them to continue to feel the progress of their work.
3) do not do "no employment": Determine which to do, to achieve the ultimate, should not do not do
4) effective and simple:
5) Team Size: 5-9 people are the most suitable

9. Three Prerequisites:
1) Organizational structure:
2) Personnel ability and quality:
3) Team Culture:

10, the requirements of personnel:
1) Strong technical ability
2) Versatile
3) Automatically work spontaneously
4) team-oriented

11, the basic concept:
1) The Scrum framework implementation does not have the so-called best concrete practice, only more suitable, more effective practice, the implementation of scrum is not because you are now in my good, but in your next month
There's no getting better.
2) The implementation of scrum, not only refers to the technical level of transformation, but also means that the concept of innovation; the change of work practice is only one aspect, the change of concept is a completely different side
3) Implementing scrum requires not only a change in the project team but also a change in the entire organization
4) The key to successful implementation of SCRUMR is the combination of top-down and bottom-up changes
5) There is no end to scrum improvement, it is a continuous improvement process.
6) We are all in a boat.
7) Everyone is responsible for the success of the project.
8) Team decisions, not leadership decisions
9) All people work directly with the demand-driven.
10) Everyone needs to work across areas.
Scrum is simple, but not easy.

12, the development of the overall process

13. Three main elements of user stories
1) as a < user type >
2) I want to < a goal >
3) for < some reasons >
Examples of user stories:
As a new user, I can register by creating a username and password so that the system can remember my personal information

14. Suggestions
1) Change the environment and create an atmosphere
2) training before, implementation in the post
3) pilot in front, promotion in the post. Test whether it is suitable, and then spread out after successful pilot
4) The overall "specification", progressive "agile". Introduction of Agile in local
5) Keep exerting force and break free from "Gravity". Persist, or they will be dragged down by traditional forces.
6) Supporting incentive, "inside", "outside" concurrently repair.
Recommended Books:
Scrum Agile Software Development, user stories and agile methodologies

Scrum Agile Project Management essentials