Jun Lu Pmp Mba Email Address

Manager of Data Science ; PMP#233293; Business Intelligence and Data Analytics and Data Science; App Developer

Kinder Morgan is an energy infrastructure company that transports natural gas, gasoline, crude oil, carbon dioxide etc.

“Is it possible to do the same project twice?” Theoretically, but it never happens in practice. So how does one know with certainty if the project could have been done better? With lower budget? Shorter timeline? Or better user experience? The fact is software construction projects are hard to measure. It’s often done with subjectivity rather than objectivity. Elements surrounding the project such as a company’s culture, senior management members’ own experience, the placement of IT on the company’s strategic totem pole can greatly skew the measurement of success. What about the estimates and timeline? Too often they are self-fulfilling. How often are prioritizations done with true ROI as a key decision factor? At what point do we say user experience is good enough and when do we call it ‘gold plating’? Is long term maintenance cost carefully considered during the budget and design phase? The more you dig into it, the more it appears that effective measurement of success is somewhat a fairytale in the kingdom of software construction. So how does senior management determine if a $1 million project could be done with $500K? Will the quality suffer? Will the feature list get cut in half? I do not know is there is a black and white answer to the questions. However, I have always followed the principles and processes below, and have been able to deliver numerous mission critical projects on time and under budget. 1.Build a supportive environment that fosters teamwork and innovation 2.Putting the right people to the right jobs 3.Action over planning 4.Understand end-users’ needs and drive the products to meet those needs 5.Rigid quality assurance processes at every stage of software construction 6.I deep dive often 7.Agile development is more culture than processes 8.Challenge the estimates, require each module to be no more than 4 hours of work. 9.Foresee problems and come up with innovative solutions.