Managing Software Projects
-
What you're asking for is impossible. What makes our opinions better than those presented in books ?
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
-
There's a lot of books and Internet resources available on the subject. Personally, I'd suggest reading up on those and then coming back and asking a more specific question. Otherwise, I think you're only going to get vague answers like: Don't stifle creativity with processes and policies Make sure they make sense Follow them Encourage communication, code reviews, testing, customer involvement (if applicable). Review milestones, estimates, and revise to maintain a realistic schedule and work hours. Keep the refrigerator well stocked. Oh, BTW, you can spend 1-6 man months just arguing and creating the policies. You can spend another 1-6 man months trying to enforce them. Rather than creating p&p's for managing 2-3 developers, why don't you try finding 2-3 developers that are capable of managing themselves? Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh SmithMarc Clifton wrote:
Rather than creating p&p's for managing 2-3 developers, why don't you try finding 2-3 developers that are capable of managing themselves?
Which do you think is harder?
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighist -
Marc Clifton wrote:
Rather than creating p&p's for managing 2-3 developers, why don't you try finding 2-3 developers that are capable of managing themselves?
Which do you think is harder?
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighist -
Marc Clifton wrote:
Rather than creating p&p's for managing 2-3 developers, why don't you try finding 2-3 developers that are capable of managing themselves?
Which do you think is harder?
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
My first real C# project | Linkify!|FoldWithUs! | sighistpeterchen wrote:
Which do you think is harder?
That is a hard question. Probably the latter--developers that can manage themselves. After all, that takes more experience--usually the hard knock, several failed or near-failed projects experience. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
Please share practical guidance based on your experiences on creating processess and policies for managing small (1 - 6 Man Months) software projects with 2-3 members developer team
csb
I wish I could give you a simple answer, but when it comes to Project Managment there are no 'simple' answers. Please check out http://www.pmi.org/info/default.asp[^] for a list of great resources. If you wish to fully understand PM but avoid the usual blather on the subject then I suggest reading Undaunted Courage, My Years at General Motors, Nothing Like It in the World, and Joel On Software.
Learning is not a spectator sport. - D. Blocher
-
I would love to hear from the senior guys out here on how they actually are managing the projects Regards
csb
FUD.
Deja View - the feeling that you've seen this post before.
-
Please share practical guidance based on your experiences on creating processess and policies for managing small (1 - 6 Man Months) software projects with 2-3 members developer team
csb
Like others have said, I'd suggest reading up and coming back with specific questions.
stskpa wrote:
creating processess and policies for managing small
For a small team on a project that you are attempting to deliver quickly I'd suggest that you keep them "lightweight" and automated. Small teams can't afford the overhead of overly complicated or time consuming processes.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
FUD.
Deja View - the feeling that you've seen this post before.
Pete O`Hanlon wrote:
FUD.
Reminds me of the following story: A Texas billionaire is holding a party for his exeptionally attractive 21 year old daughter and all the eligible bachelors in the state are invited. As the evening progresses he asks them all to stand at one end of his olympic sized swimming pool while he addressed them from the other with his beautiful daughter by his side. He announces that who ever is the first to swim across the pool, which is filled with alligators, can have his choice of three prizes. One prize is $5million. Another prize is some of his prime cattle ranch property which brings in over $10million in profit each year. Or the final prize is his daughter's hand in marriage half of his estate now and the other half as an inheritance. No sooner than he finished his announcement there was a splash at the far end of the pool. Moments later one of the young men hauled himself out of the pool in front of the billionaire soaking wet with his tuxedo in ruins. "Well, son. Is it the $5 million you want" asked the billionaire. "No, sir" the young man replies. "Would it be the Cattle Ranch that you want?" asked the billionaire "No, Sir" the young many replies once again. "Then I take it you want the hand in marriage of my beautiful daughter" "No, Sir", the young many replies yet again. Confused, the billionaire asks "Then what do you want?" "Sir, I want to know the name of that dude that pushed me in the pool"
Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website
-
Pete O`Hanlon wrote:
FUD.
Reminds me of the following story: A Texas billionaire is holding a party for his exeptionally attractive 21 year old daughter and all the eligible bachelors in the state are invited. As the evening progresses he asks them all to stand at one end of his olympic sized swimming pool while he addressed them from the other with his beautiful daughter by his side. He announces that who ever is the first to swim across the pool, which is filled with alligators, can have his choice of three prizes. One prize is $5million. Another prize is some of his prime cattle ranch property which brings in over $10million in profit each year. Or the final prize is his daughter's hand in marriage half of his estate now and the other half as an inheritance. No sooner than he finished his announcement there was a splash at the far end of the pool. Moments later one of the young men hauled himself out of the pool in front of the billionaire soaking wet with his tuxedo in ruins. "Well, son. Is it the $5 million you want" asked the billionaire. "No, sir" the young man replies. "Would it be the Cattle Ranch that you want?" asked the billionaire "No, Sir" the young many replies once again. "Then I take it you want the hand in marriage of my beautiful daughter" "No, Sir", the young many replies yet again. Confused, the billionaire asks "Then what do you want?" "Sir, I want to know the name of that dude that pushed me in the pool"
Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website
:laugh:
-
Please share practical guidance based on your experiences on creating processess and policies for managing small (1 - 6 Man Months) software projects with 2-3 members developer team
csb
1. Have a good team. 2. Have a clear idea. 3. Have a leader. 4. Have enough money. 5. Go for it. I'm serious though. Anything else is Project Management That Worked Once So Now I Am Milking It With This Book But No Guarantees It Will Work For You. So many of the best projects in IT have been a bunch of gifted guys with a singular vision going hell for leather. No process, no methodologies or management best practices. You can have all the Agile Prince2 Bullshitter methodologies you want but if the team and idea is horse meat you might make a burger but it will take some serious dead-horse beating to get there. On the other hand if it is horse meat you are working on; I like the Agile methodology. Use something like XPlanner for tasks, Bugzilla for bugs and do two week iterations. Do a round over coffee each morning on what each person is doing and keep reassesing what needs to be done. Try to avoid tangents and distractions, stick to the original plan. :) (Not bitter, cynical or tired at all. Just sick of "Do X, Y and Z and it will work" 'cause it doesn't.) 3. can be more than one person but they'd better be a brilliant pairing to avoid rifts.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
And with that, Paul closed his browser, sipped his herbal tea, fixed the flower in his hair, and smiled brightly at the multitude of cute, furry animals flocking around the grassy hillside where he sat coding Ruby on his Mac...