Justin WortleyProject Manager| Quicken LoansDetroit, Mi, United States
Due to some restructuring I'm going to have to take a much more hands on approach with our risk management and cost management in our projects. Traditionally I've done infrastructure PM work of which both of these areas have been mostly black and white (I say mostly ;) ), but we're shifting into software development which I don't have a ton of practical experience with when it comes to risk management and budgeting. Are there any good resources out there that could get me up to speed on how to best approach these two areas so that I can hit the ground running? The dynamic nature of software development vs the traditional approach of infrastructure work gives me concern that I need to research as much as I can. Saving Changes...
Sort By:
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
The big thing to watch, Justin, is the over-reliance on testing as the sole risk mitigation process for software quality. Because testing is usually at the end of the project, it can really wreak havoc on your schedule.
I usually push for a lot more QA activities: peer review, walkthroughs, audits. Saving Changes...
Justin WortleyProject Manager| Quicken LoansDetroit, Mi, United States
Thanks Stéphane - I had considered testing in my initial research but I hadn't considered the volatility that it could have when it comes to the actual schedule. I'll make sure to keep the QA activities broad so I can keep the schedule in front of me, rather than chasing it if it gets away from me later. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Agile can somewhat help reduce the impact of testing on the schedule. When it comes down to it, the only way your customer will accept a new application is after they test it. Try to get as much visibility in the acceptance testing as you can. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Nothing new than in other type of initiatives. Regarding to budged, the only characteristic that is particular to software is the method you will use to estimate the work. As you know, software is intagilble so that is a critical point. But regarding risk and issues there is nothing new. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
To follow on Sergio's point about software estimation, you can estimate software size by input (effort to produce) or by output (lines of code or function points). If you don't have an organizational output index to convert the output into effort, you can always use industry-wide indices. Saving Changes...
John Caron, MBA, PMP, CSMVP - Technology Project Solutions Consultant| Bank of AmericaJacksonville, Fl, United States
Justin, at work, do you employ Waterfall, Hybrid or Agile approaches? Saving Changes...
