First, the user analysis
1, lateral: User's said and done
how that performance goals and perspectives, how do reflect the behavior, how do users say and how often inconsistent,
2, longitudinal: qualitative and quantitative
qualitative research can find out the reason, tend to understand,
quantitative research can discover phenomena, tend to confirm that
the iteration:
① listen to user qualitatively
determine the direction of the product, what to do?
② listen to user Quantitatively
determine priority needs, what to do first?
③ look qualitatively user to do
that a few needs to do first is, how we should do?
④ see quantitatively user to do
after data analysis, continuous improvement of products
Second, the incremental interviews to get as correct conclusion
Third, the requirement type:
1, Category:
new features, improvements, to enhance the experience, BUG, internal demand
2 levels:
basic, extended (expected demand), value-added (excited demand)
Fourth, the project team meeting
① progress How
② the need to adjust the schedule
if ③ need additional resources
if ④ there is significant demand change
how ⑤ published project data performance
⑥ have any problems, risks and countermeasures
Five, product manager VS project manager
, product manager: by want to do the right thing, whether they are leading products in line with market demand, is to give the company a profit,
project manager: by doing, doing the right things, do things perfectly, in time, cost and resource constraints under the conditions of the completion target,
six workload assessment
workload = (most optimistic + pessimistic + most most likely) / 3
or workload = (most optimistic + pessimistic + most most likely * 4) / 6
VII. VS process
project only once, so the pursuit of feasible solution; processes to repeatedly done, the pursuit of the optimal solution,
long the viewer when the purpose of the means, the means when the purpose of short-sighted person,
eight projects KO
1, project background
where we are clear why to do this project
2, project meaning, purpose and objectives
where we go, mark a bright future, the success of
3, demand, function points Overview
How we go, what means
4, project organization
clear what happened should go to who
5, the project plan
① point in time and project milestones
② each period needed resources / each person to do anything at all stages
6, communication plan
Regular meeting, minutes of meetings
9, the project documents
1, BRD: Business Requirements Document
duration analysis, sales strategies, profits in the
2, MRD: Marketing Requirements Document
meticulous long and competitor analysis,
what features to achieve commercial purposes,
functional, non-functional demand points which few, function and priority
3, PRD: product requirements document
whole description, use case documents, product Demo
4, FSD: functional details, outline design
product interface, business logic details of
ten, PRD specification
1, Revision history date , version number, description, and author
2, an overview of the project background, meaning, purpose, target
3, the functional scope of business logic diagrams, system roles and responsibilities
4, the scope of the role of the user, the system
5, glossary technical terms, terminology, abbreviations
6, non-functional requirements performance requirements, data monitoring requirements
7, additional instructions
XI, agile development
1, there are plans, but also to embrace change
2, the inner iteration trying not to task
3, concentrated work, small run
4, continued refinement demand, emphasizing test
5, continue to publish as soon as possible to deliver
XII morning will stand
when Less than 20min
per person:
1, yesterday did what? How the overall progress of the task?
2. What to do today?
3, any problems, intends to solve, what it takes to help
XIII, as far as possible week released three new versions of
XIV cooperation projects
clear mode of cooperation, such as division of powers and responsibilities to
enjoy the benefits of things can be done, but also responsible for the failure of loss ; must not do something that has the ability to take on the task,
XV model of cooperation within the company - to work for the profit of
the service sector profit work yesterday, commitment to provide value to
the sales department for today's profit work for customers,
the development of sector-profit work tomorrow, tomorrow to ensure excellent product ,
research department working for the profit acquired, pre-research and trends to grasp,
sixteenth and management principles
rely on rules of management, rather than being managed
seventeenth and management
objectives: what I do, you bear the blame back, their duties
so-called growth:
let the boss do quiz -> let the boss do multiple-choice questions -> let the boss do determine the question
who make decisions, who scapegoat
eighteenth and VS management leadership
management is more like science, like art of leadership,
management of test sites is power leadership relies on charm
management systems emphasize stability, leaders adventurous
manager who according to law, the leader virtuous
object management is the behavior of the object is thought leadership
management tube doing things right, leadership is doing the right thing tube
step by step, the leadership does not take the unusual way the management of
the tube Managers focus on short-term goals, leaders focus on long-term development,
managers are professional managers, leaders and entrepreneurs entrepreneurs
manage a car's braking system, leading automotive drive systems
management is to tell the team how to do, leadership is Why tell the team to do,
affect the management of people from outside to inside, giving the power of leadership from the inside out
management allows teams to accomplish these things, let the team leaders like these things
ninth, news
The good news for twice that bad news will say together,
big good news and bad news, said with a small,
little good news and bad news, said separate large,
XX, the statement highlights
small success by friends, big the success depends on the opponent,
the General Assembly decided to trivial, small events will be decided,
for all advice, few people are talking, a man clappers
strive to "thinking, live too old to learn," thinking skills, ability to learn is "school did not teach things, "our education tell us the answer too many questions, but forgot a lot of problems in life is" only method there is no answer, "the
please Give me the strength to accept what I can not change, please grant I have the courage to change what I can change, and grant me the wisdom to know the difference,
- "World of Warcraft - Wrath of the Lich King", silver Antonidas
holding a hammer, to see what is like nails,
wanted to nail a nail, to see what are the hammer,
occasional thing, only feasible solution, often do pursue optimal solution,
Finally, a few feel useful chart for reference
1, meeting minutes templates
2, the full project cycle
3, demand cycle
4, demand card template
