Practical summary of the project development and management

2010-08-21  来源:本站原创  分类:Development  人气:51 

Practical summary of the project development and management

2010-8-21

Recently with several members of the group project development, in order to avoid in 2009 led the project in Guangxi Unicom mistakes, time to do some summary records, in order to constantly remind himself not to commit the same problem.

First, focus

1: Requirements Capture and Analysis
2: Task decomposition
3: Effort Estimation
4: task prioritization
5: Resource access and authorization
6: Project progress tracking
7: deal with unexpected problems

Second, the specific details

Requirements capture and analysis to be as accurate as possible, to avoid rework. Can be combined with pre-prototype Demo, as many communication, allowing customers to determine needs.
UML and the like can not be too complicated. Just to aid understanding of the requirements, as well as communication and members understand the tasks on the line.
Members understand the strengths and ideas, reasonable arrangements for the task.
Task decomposition granularity as small as possible, to facilitate tracking and workload estimates.
In the project, we are not familiar with the technology used, the workload estimate * 2.
Task estimates, to arrange for people with mobility and motor time, should not be completely filled in order to deal with unexpected things.
Ability of members to be complementary, not everyone do the same thing.
Guide members of the rational organization of work: work experience, especially people who have just graduated and soon encounter something new, always trying to learn that this is science, not according to plan. Should let them know, to progressively complete the task. Complete the work first, then learn. To learning at work, rather than in learning the job done.
Use of new technology, the relative wealth of people have experienced a unified training, and not let members of the laissez-faire, self-learning is not easy to seize the key, more important is to learn something, not necessarily useful to the project.
Have a good management tool and version management tools, unified training to avoid the use of tools errors waste of time.
Equipment and have someone manage to configure the environment to prevent the effects work.
Documents and specifications, are also important. To avoid the accumulation of technical debt later. Long-term projects, such as the kind of period N, there is no corresponding documentation, maintenance of the people behind it will be very painful. Especially in face of members of the big shake-up, the more apparent. For a project, the company will consider the company's cost, schedule, benefits, etc., so not all will be very seriously. However, debt is always someone to have, and I hope people themselves do not become insolvent.
Problems should be thrown outward and upward, not into a dead end, that difficult things their own, others may be easy to solve, to learn the rational use of team resources. Higher complexity of the task to know, good for resources and adjust task.
Motivate team members to improve the level of the plot work.
Members of the execution is very important.
The person authorized to be higher.
And members often communicate progress and problems encountered, can be as small working days.
The progress of the initiative and superior communication.
Human resources can not be easily changed. To the parent that has called the arrangement a member of the Task Scheduler can not guarantee the smooth progress.
Do not have to do things the pro-bow, we should put out the task, grasp the overall. For experienced people, to trust and delegation of authority, as long as the guidance and tracking on the line. Themselves are not necessarily smarter than others.
Have incentives, such as Money and the like, or else we no enthusiasm, but by the Boss to decide this, not people themselves motivate it, ha ha. Can only be disguised from the rest on the incentives.

相关文章
  • Practical summary of the project development and management 2010-08-21

    Practical summary of the project development and management 2010-8-21 Recently with several members of the group project development, in order to avoid in 2009 led the project in Guangxi Unicom mistakes, time to do some summary records, in order to c

  • Practical project development and management summary 2010-08-21

    Practical project development and management summary 2010-8-21 Several members of the group recently carried out with project development, in order to avoid in 2009 led the project in Guangxi Unicom mistakes of time to do some summary records to cons

  • Project Development Process Management 2010-07-01

    Project Development Process Management (A) Svn as program code, and various versions of a document management tool 1) backbone as the main line of development 2) the branch as a phased upgrade 3) system on-line asset management system for on-line cyc

  • Project development and management 2011-07-19

    Project development process is divided into four stages: the initial phase of the project, system design and build phase, the product phase, maintenance phase. Including system design and construction phase would normally produce multiple iterations.

  • Technical summary of the project development process 2010-05-28

    Many details of the project design stage, often unexpected, but to the actual development when it is discovered that in fact not so simple, following the development process will be used in some small technical summary of what. 1, struts the doublese

  • Transfer some of the new project development and summary 2011-02-08

    Done has been in development for some time, some situations encountered during the period. Here are some of my personal review and experience. How early in the project signed with the client to talk about, this place can be a lot of embellishment, gi

  • How to use software development project scope change management 2011-03-17

    How to use software development project scope change management Source: FRANCISCO project management process does not determine the project from the beginning, nor end with the completion of the project plan. You have to use the project management sc

  • XX quick summary of the project practice 2010-07-01

    XX quick summary of the project practice XX took over the project and found that this project has the following risks: 1, demand uncertainty (completed until four weeks after the start of the project requirements) and full of change (and the tree of

  • "FPGA embedded real project development" 2009-10-17

    Actual FPGA embedded project development / edited by Liu forge .- Beijing: Electronics Industry Press, 2009.4 (Embedded development specialists) ISBN 978-7-121-08220-7 Size: 787 × 1092 1 / 16 Sheet: 29.75 words: 761.6 thousand words Printing times: A

  • [Change] Defects and Solutions - a game developer's Reflection 2. Project development in the chaos and order 2010-04-16

    Second, project development and order in the chaos We may have heard these statements: "You can not something for nothing" "spilled" or "Justice has long arms." If the proverb is not strange to you to say, and repeatedly in e

  • LAMP project development process rules 2010-07-01

    LAMP Project System is the performance of the three-layer, application layer and data storage layer composition. Performance is made up of Web browser form, the data for the performance of the application layer or application layer of the data throug

  • We talk about the development and management philosophy - is reproduced 2010-07-10

    Original: http://www.javaeye.com/topic/508928 Recently heard too much from the software industry, "project manager" story, in fact, the framework can be fabricated with several technologies used; or casually say write what framework, and then ta

  • Project Development Quanji Lu (a) 2010-12-19

    1, environment development process, the first day is often identified project development framework and development environment at the same time build a good development tool: MyEclipse Database: MySQL 2, add SSH support the order: A. Spring B. Hiber

  • Easier software development risk management - at 2007-02 <Programmers> 2007-03-05

    Some time ago I wrote a blog, called "game, great truths." On a called "ColorLinez" little game. Although the surface is a summary of the game strategy, and my mind has been pondering, or development and management matters. This time &

  • Small and medium sized software project life cycle management experience at all stages 2009-01-23

    I am small and medium sized software development companies in the two worked for several years, also did a few years of project management. Some have come through a number of detours project management experience, in this summary, I hope to work with

  • We talk about the development and management concepts 2009-11-02

    Recently heard too much from the software industry, "project manager" of the story, in fact, can be used with a pile of several technical framework; or what to write frequently say their framework, and then discuss how frameworks such as struts2

  • Summary of my project 2010-03-03

    Website v2.0 project impressed me a few things most children: I am sorry I did not direct the project team members as being involved in the project, but project development process I have been very concerned about, I believe we all felt (do not feel

  • [Transfer] defects and a way out - a reflection of two game developers project development in the chaos and order 2010-04-16

    Second, the project development of chaos and order We may have heard the saying: "You can not something for nothing", "turning back" or "Justice has long arms." If the proverb is not strange to say to you, but also in everyda

  • The development of the software development team management 2010-05-10

    Introduction: In the increasingly large-scale software development and refinement of today, how to manage a team, how to lead their team to success, to adapt to various types of complex software development projects, has increasingly become a very te

  • Project development process - reproduced 2010-08-04

    A software engineer software process summary Simple Design The basic stability of the current development framework, the design of specific business delayed, developers can design a simple interface and quick access to specific versions of iterations