PMS Programming with .NET

[Cindy Lee]

I've created a small guide to software methodology called PMS
programming. I hope it can redefine project
management and get rid of SCRUM meetings. Puts the focus on Project
Management Software (TFS) and stubborn developers (who like .NET MVC)

Just wanted some feed back. Is the name good? Hate my points? I
don't want to ask anyone I know and get a sugar coated answer.

http://pmsprogramming.com/

 

[Peter Duniho]

I've created a small guide to software methodology called PMS
programming. I hope it can redefine project
management and get rid of SCRUM meetings. Puts the focus on Project
Management Software (TFS) and stubborn developers (who like .NET MVC)

Just wanted some feed back. Is the name good? Hate my points? I
don't want to ask anyone I know and get a sugar coated answer.

http://pmsprogramming.com/

I found nothing in the article that was actually specific to .NET. Why is
it "PMS Programming with .NET"?

As far as feedback goes, it seems a lot of the article has to do with
other than actual project management. That is, you discuss topics that
can be managed as part of a project, and thus could be represented in
project management software, but which aren't really about project
management per se. Are you trying to discuss project management itself?
Or the things that go into a sucessfully run project?

With respect to project management software specifically, it seems to me
that one of the important features (if not the most important) that
project management software offers is the ability to track dependencies
and arrange the work so that it can be completed in the most efficient
manner. But there's nothing in your article that discusses this. Of
course, there's very little in the article that discusses project
management software at all, never mind how to most effectively use it.
But certainly the dependency-tracking feature is one that you should talk
about.

Finally, I can't tell whether this was intentional on your part or not,
but "PMS" is a well-known abbreviation in the US, for "pre-menstrual
syndrome". Ignoring for the moment why "Dan" is using the name "Cindy"
, it seems to me that it's either not a very good joke (might alienate
some people, and not just women) or it's just the wrong name altogether.

Pete

 

[Cindy Lee]

I found nothing in the article that was actually specific to .NET.  Whyis  
it "PMS Programming with .NET"?

As far as feedback goes, it seems a lot of the article has to do with  
other than actual project management.  That is, you discuss topics that 
can be managed as part of a project, and thus could be represented in  
project management software, but which aren't really about project  
management per se.  Are you trying to discuss project management itself?  
Or the things that go into a sucessfully run project?

With respect to project management software specifically, it seems to me  
that one of the important features (if not the most important) that  
project management software offers is the ability to track dependencies  
and arrange the work so that it can be completed in the most efficient  
manner.  But there's nothing in your article that discusses this.  Of 
course, there's very little in the article that discusses project  
management software at all, never mind how to most effectively use it.  
But certainly the dependency-tracking feature is one that you should talk 
about.

Finally, I can't tell whether this was intentional on your part or not,  
but "PMS" is a well-known abbreviation in the US, for "pre-menstrual  
syndrome".  Ignoring for the moment why "Dan" is using the name "Cindy" 
, it seems to me that it's either not a very good joke (might alienate  
some people, and not just women) or it's just the wrong name altogether.

Pete

Thanks for your input. I couldn't find a group about TFS server, so I
posted it here and partly to get a developers point of view.

Yeah, I'm more encouraging people to read books or articles about
their Project Management software instead of telling them how to use
it. I don't want to make the article much longer. I should add
something about dependency track though, thanks I'll try to add that.

And you're right it might be more about how to sucessfully run
project. I'm still working on things, so I might take some of the PM
stuff out.

The PMS is on purpose, mostly because I think names of many
methodoligies are really stupid like 'extreame programming'. Also to
get people to wonder and click on the link. I was going to call it
Rad programming.

About the Cindy, I've had it for a while. I've found that people
respond better on news groups when I use the name Cindy.

 

[JS]

Sounds to me like your trying to mix Project Management with
SCM (Software Configuration Management) and other methodologies,
with a pinch of the old software programmer grips for good measure.

You point out some of the many problems but have no cohesive solution.
Take a look at cmcrossroads: http://ww.cmcrossroads.com there are
plenty of white papers on this and other subjects.

Sorry to be so hard on you, but if you going to stick your foot
in the water be ready for the sharks ;-)

 

[Cindy Lee]

Sounds to me like your trying to mix Project Management with
SCM (Software Configuration Management) and other methodologies,
with a pinch of the old software programmer grips for good measure.

You point out some of the many problems but have no cohesive solution.
Take a look at cmcrossroads:http://ww.cmcrossroads.comthere are
plenty of white papers on this and other subjects.

Sorry to be so hard on you, but if you going to stick your foot
in the water be ready for the sharks ;-)

No, please be as harsh as possible, it's great input. Call me an
idiot if you want, I don't expect everyone to agree with me especially
on usenet groups. And I still have stuff to learn and reword part of
this article, this feedback is great.

I agree with your first paragraphic, it is a mix of things. I
added the programmer gripes after my first draft. I just thought it
was part of getting a project done on time. I'm just seeing a large
trend of people using ASP.NET MVC (which I think is wrong).


Thanks for the crossroads site. It's exactly what's I'm against and
why I wrote that article. Take the 1st page:
"Webinar: Cut Development Costs and Speed Innovation with Agile
Did you know that Agile development can decrease your time-to-market
by 50% and increase productivity by 25%?"
The typical project manager is going to read that and think they can
fix their problems. Everyone on that site will be against me.


As for "no cohesive solution", you're right again. I don't offer
solutions. My point is to read books about your Project Managment
Software (TFS, jira...) instead of a book on agile development. As
for solutions, your lead developer needs to come up with them and lead
you down the right path.

 

[JS]

You're partially correct about SCM.
But at least some of the SCM problems come
from both the developers who fight and resist SCM
because it crimps their style and managers who
haven't got a clue as to what really goes on during a
development effort.

If you are going to ask me which one of these
groups I was involved in the answer is all three and
more. Software Developer, Software Quality Control,
Principal Programmer Analyst, Project Leader and SCM Administrator.

Good luck on your effort as I'm sure you will find a
lot of useful and interesting information.

--
JS
http://www.pagestart.com

Sounds to me like your trying to mix Project Management with
SCM (Software Configuration Management) and other methodologies,
with a pinch of the old software programmer grips for good measure.

You point out some of the many problems but have no cohesive solution.
Take a look at cmcrossroads:http://ww.cmcrossroads.comthere are
plenty of white papers on this and other subjects.

Sorry to be so hard on you, but if you going to stick your foot
in the water be ready for the sharks ;-)

No, please be as harsh as possible, it's great input. Call me an
idiot if you want, I don't expect everyone to agree with me especially
on usenet groups. And I still have stuff to learn and reword part of
this article, this feedback is great.

I agree with your first paragraphic, it is a mix of things. I
added the programmer gripes after my first draft. I just thought it
was part of getting a project done on time. I'm just seeing a large
trend of people using ASP.NET MVC (which I think is wrong).


Thanks for the crossroads site. It's exactly what's I'm against and
why I wrote that article. Take the 1st page:
"Webinar: Cut Development Costs and Speed Innovation with Agile
Did you know that Agile development can decrease your time-to-market
by 50% and increase productivity by 25%?"
The typical project manager is going to read that and think they can
fix their problems. Everyone on that site will be against me.


As for "no cohesive solution", you're right again. I don't offer
solutions. My point is to read books about your Project Managment
Software (TFS, jira...) instead of a book on agile development. As
for solutions, your lead developer needs to come up with them and lead
you down the right path.