My note on: what is project and how should we proceed and close project successfully.
A project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.
And a project is unique in that it is not a routine operation, but a specific set of operations designed to accomplish a singular goal. So a project team often includes people who don’t usually work together – sometimes from different organizations and across multiple geographies.
The development of software for an improved business process, the construction of a building or bridge, the relief effort after a natural disaster, the expansion of sales into a new geographic market — all are projects.
And all must be expertly managed to deliver the on-time, on-budget results, learning and integration that organizations need.
From : https://www.pmi.org/about/learn-about-pmi/what-is-project-management
5 steps in project management.
- Monitoring and Controlling
- Call on right people with clear goal.
- Communication method
- What needs to be bought, subscribe order
- Write all to do (Gannt Chart), Feature, Story, Tasks
- Risk management
- Just do it
- Are assignments OK?
- Is it on schedule?
- Is quality OK?
- All scopes are staying within scope?
- Is initial risk management good enough?
- Check and see if project has 1 come to the end of schedule, 2 complete objectivity.
Agile project management is about
- continuous improvement
- scope flexibility
- team input
- delivering products
which are all great things when it comes to developing web services in team. If you want to run a well managed project, read http://www.dummies.com/how-to/content/agile-project-management-for-dummies-cheat-sheet.html and follow.
On the other side of agile there is a waterfall style development. These two models have pros and cons. Please read, http://www.base36.com/2012/12/agile-waterfall-methodologies-a-side-by-side-comparison/.
When you are to go after some issues or building strategies, one of the effective approach is to have hypotheses driving thinking.
What is hypotheses driving thinking?
That is to build the best guesstimated answers to occurring problems at that moment.
It is the best answer as of this moment snapshot.
As clean and effective data are generated as time goes by, the answer may be different from your hypotheses, and that’s even OK. The hypotheses has a purpose as a guides to problem solving and not necessary need to be an answer.
Why is this good or need it?
Things are uncertain, not clear, there is no person that knows everything or can answer everything, therefore having hypotheses and start building data and strategy sometimes is the best you can do.
Good and not so good hypotheses.
Your good guesstimated answer can even be better one
by checking followings;
Think and see things from the other side. Imagine being the user, being the competitor, being in the field.
Think and see things from two extreme sides.
Think and see things from clean start. Forget everything you know and think for now, start fresh from zero.
And in order to solve problems, the hypotheses must drive actions. So, think about how you want to drive actions from your hypotheses too.
more to continue.
My memo for, when you have millions of to-do and marking proper priority.
- Decide what I don’t do, instead what to do.
- Segment 1 to do into multiple to do. Make 1 big to do into small to-do.
- Cross out old to-do. (sorry old to-do)
- Put due day a day early (.. like this is possible??)
- Be specific about to-do action.
- Don’t worry so much about priority.
- 70% is good enough. (indeed there is always tomorrow, and day after tomorrow)
- Put your to-do in matrix like below instead of in list style.