Win a copy of Programmer's Guide to Java SE 8 Oracle Certified Associate (OCA) this week in the OCAJP forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Thin line between the project management and the Developer

 
Vijay Kalkundri
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

It is generally observed that the software engineers/developers are more interested in the technical details of the project rather than the management of the project as a whole. The product manager/bussiness analyst is more bothered about the requirements/bussiness angle of the project. Hence there is a disconnect between the 2 community.
Due to this there a lack of understanding of the market needs/ customer needs in the developer community and lack of understanding of technical intricacies in the product manager or bussiness analyst.

1) What is that changes that should be brought in the mindset/working way of these 2 community ppl so that each one thinks from anothers anagle and the management of the project/product is a smooth one ?
2) What should be the quality bechmark for the management before the product goes to market ?


Regards,
Vijay Kalkundri
 
Rahul Goyal rg
author
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Hi Vijay,

Great Questions! and tough ones to answer.

Vijay Kalkundri wrote:

1) What is that changes that should be brought in the mindset/working way of these 2 community ppl so that each one thinks from anothers anagle and the management of the project/product is a smooth one ?

Some of things that may help: Vision of a common goal & clarity in roles & responsibilities.

If someone can articulate and lay down the 'outcome', what success looks like and how it will be achieved by contributions from each community.
Another is the 'incentives' managers place on collaboration, so engineers and managers are encouraged to collaborate.

Vijay Kalkundri wrote:
2) What should be the quality bechmark for the management before the product goes to market ?


This is very situational and varies highly based on what the purpose of the product is and also the market characteristics where product is to be launched.
For example, Mobile phone apps are fairly easy to build, however, the consumer expectation is very high on initial usage experience. Any application that doesn't work well in first of second try will loose traction very quickly.

Compare that to an online time-reporting tool vs embedded software...

What is perhaps most important is to SET a quality bar at the start of the program that is clearly understood by the development & quality team.

Thanks
Rahul


 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic