Any tips/tricks/suggestions/insights would be welcome.
Project Management
Moderator: General Moderators
-
kettle_drum
- DevNet Resident
- Posts: 1150
- Joined: Sun Jul 20, 2003 9:25 pm
- Location: West Yorkshire, England
Project Management
Was just wondering what methods people use to manage projects. What software do people use? What do you think the pros/cons are of managing projects in different ways? Any good papers/articles/tutorials on the subject?
Any tips/tricks/suggestions/insights would be welcome.
Any tips/tricks/suggestions/insights would be welcome.
I havent really been looking around for tutorials on the mather.
Ofcourse you will come across some of them, but they will only explain they way they do it.
( i would consider this like making a choice for a web language ) we have all heard it a million times and even said it a couple of times ( i think )
Should i code in php / asp / javascript / java / c ........ect : Whatever feels good to you , am iright ?
However i have these:
Pen and Paper : i have learn to love them when it comes to db design.
Visio m$:( but handy when it comes for having a visual layout for a number of things.
Ofcourse you will come across some of them, but they will only explain they way they do it.
( i would consider this like making a choice for a web language ) we have all heard it a million times and even said it a couple of times ( i think )
Should i code in php / asp / javascript / java / c ........ect : Whatever feels good to you , am iright ?
However i have these:
Pen and Paper : i have learn to love them when it comes to db design.
Visio m$:( but handy when it comes for having a visual layout for a number of things.
The requirements for project management depend very much on what level you are involved. For developing applications as a project manager the minimum you should take care of:
1. Document outlining application spec and functionality
2. MS Visio: Application Workflow Diagram
3. MS Visio: UML class diagram
4. Review 1.-3. and see if all describe the same workflow and functionality
5. Programming the API
6. Review 5. to see if it actually fulfills what 1.-3. set out to do
7. Program code
8. Create documentation with phpdocumentor
9. Refine API & code where necessary
10. Test, test, test (if you have can, unit-test)
11. Test some more
12. Test a little bit more with other people involved as well
13. Praise everyone you've worked with and get them to buy you beers.
14. Run some tests just to make sure.
That's just a very, very, brief outline: the most important things to me are
1. clarity at all levels and for everyone involved
2. clear structures
3. KISS: keep it simple, stupid.
4. Always think about your application as if you were looking back at it from 2 years on.
Just another thing: have a look if a similar project exists somewhere - if so: great, you can probably learn something.
For some background reading:
http://www.sitepoint.com/article/develo ... -success/2
http://www.sitepoint.com/article/proces ... umentation
1. Document outlining application spec and functionality
2. MS Visio: Application Workflow Diagram
3. MS Visio: UML class diagram
4. Review 1.-3. and see if all describe the same workflow and functionality
5. Programming the API
6. Review 5. to see if it actually fulfills what 1.-3. set out to do
7. Program code
8. Create documentation with phpdocumentor
9. Refine API & code where necessary
10. Test, test, test (if you have can, unit-test)
11. Test some more
12. Test a little bit more with other people involved as well
13. Praise everyone you've worked with and get them to buy you beers.
14. Run some tests just to make sure.
That's just a very, very, brief outline: the most important things to me are
1. clarity at all levels and for everyone involved
2. clear structures
3. KISS: keep it simple, stupid.
4. Always think about your application as if you were looking back at it from 2 years on.
Just another thing: have a look if a similar project exists somewhere - if so: great, you can probably learn something.
For some background reading:
http://www.sitepoint.com/article/develo ... -success/2
http://www.sitepoint.com/article/proces ... umentation
- AVATAr
- Forum Regular
- Posts: 524
- Joined: Tue Jul 16, 2002 4:19 pm
- Location: Uruguay -- Montevideo
- Contact:
Addapting patrikG (linux apps), i do:
1. Document outlining application spec and functionality
1.1 Make our client (boss) sign it or approve it.
2. DIA: Application Workflow Diagram
2.2 DIA: workflow diagram of the main process
3. Umbrello: UML class diagram
3.5 Predesign the Database with DBDesigner4
4. Review 1.-3. and see if all describe the same workflow and functionality
4.5 Export the classes from Umbrello to php code.
4.6 Sync the DBDesigner4 diagram with mysql Database.
5. Programming the API
6. Review 5. to see if it actually fulfills what 1.-3. set out to do
7. Program code
7.5 Try to test each module. (unit test. see 10.)
8. Create documentation with phpdocumentor (love this)
8.5 Export the Database diagram.
8.6 Export the classes diagrams.
9. Refine API & code where necessary
10. Test, test, test (if you have can, unit-test)
11. Test some more
12. Test a little bit more with other people involved as well
12.5 Test?
13. Praise everyone you've worked with and get them to buy you beers.
14. Run some tests just to make sure.
Something extremelly important show the evolution of the project to the client / boss.
Make backups!!! if you can use CVS or some versioning software.
1. Document outlining application spec and functionality
1.1 Make our client (boss) sign it or approve it.
2. DIA: Application Workflow Diagram
2.2 DIA: workflow diagram of the main process
3. Umbrello: UML class diagram
3.5 Predesign the Database with DBDesigner4
4. Review 1.-3. and see if all describe the same workflow and functionality
4.5 Export the classes from Umbrello to php code.
4.6 Sync the DBDesigner4 diagram with mysql Database.
5. Programming the API
6. Review 5. to see if it actually fulfills what 1.-3. set out to do
7. Program code
7.5 Try to test each module. (unit test. see 10.)
8. Create documentation with phpdocumentor (love this)
8.5 Export the Database diagram.
8.6 Export the classes diagrams.
9. Refine API & code where necessary
10. Test, test, test (if you have can, unit-test)
11. Test some more
12. Test a little bit more with other people involved as well
12.5 Test?
13. Praise everyone you've worked with and get them to buy you beers.
14. Run some tests just to make sure.
Something extremelly important show the evolution of the project to the client / boss.
Make backups!!! if you can use CVS or some versioning software.