What is project management.
To be able to timetable and schedule work ahead for a project, this helps you manage time and plan work for certain tasks inside the work.
For example - Agile development
Agile software development describes a set of principles for software development under which requirements and solutions evolve through the collaborative effort of self-organising cross-functional teams. It advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. These principles support the definition and continuing evolution of many software development methods.
user involvement
- Requirements are clearly communicated and understood (at a high level) at the outset
- Requirements are prioritised appropriately based on the needs of the user and market
- Requirements can be clarified on a daily basis with the entire project team, rather than resorting to lengthy documents that aren’t read or are misunderstood
- Emerging requirements can be factored into the development schedule as appropriate with the impact and trade-off decisions clearly understood
- The right product is delivered
- As iterations of the product are delivered, that the product meets user expectations
- The product is more intuitive and easy to use
- The user/business is seen to be interested in the development on a daily basis
- The user/business sees the commitment of the team
- Developers are accountable, sharing progress openly with the user/business every day
- There is complete transparency as there is nothing to hide
- The user/business shares responsibility for issues arising in development; it’s not a customer-supplier relationship but a joint team effort
- Timely decisions can be made, about features, priorities, issues, and when the product is ready
- Responsibility is shared; the team is responsible together for delivery of the product
- Individuals are accountable, reporting for themselves in daily updates that involve the user/business
- When the going gets tough, the whole team – business and technical – work together!
http://www.allaboutagile.com/agile-principle-1-active-user-involvement-is-imperative/
small chunks
is where you take everything and split it up into small chunks to be able to process the idea and plan a lot better.
80-20 rule
project stack
the stack is useful and easy to read, the colours make it easy to follow and shows you what needs doing what needs the most attention at certain dates.
