Atlantic Northeast Software Symposium
August 8 - 10, 2008 - Princeton, NJ
Advisory Engineer @ Pivotal
Mark Johnson is a Advisory Engineer at Pivotal where he focuses on helping people learn how to apply Fast and Big Data as well as PaaS solutions to address real world enterprise challenges. Mark has worked on a wide range of technology during his career. Most recently he has focused on Groovy, Grails, and Scala as technologies which enable high quality applications quickly. Mark is active in the software community as the President of the New England Java Users Group (NEJUG) and a regular presenter to user groups and various conferences. When not working, Mark can be found riding his mountain bike on local trails and playing with his family.
Once you leave academic "hello world" projects, software development is full of unknowns which result in the high rate of project failure we see too often in industry. This presentation will cover 10 principles of software risk management necessary for project success.
During the discussion we will cover topics such as pragmatic approaches to risk capture, getting past resistance to publish risks, prioritizing risks, methods of documenting and monitoring risks to name just a couple. While this presentation is targeted to the Technical Lead and Development managers, it should also be of interest to developers and architects.
As developers we dread when management requests a project estimate. Typically, you do not have the opportunity to understand all the requirements, the team composition is unknown, and you have been given until tomorrow end of day to produce an estimate. Several months later everyone is yelling at you about the software estimation errors encountered during the project.
This presentation will cover some simple techniques for creating order of magnitude estimates. In addition, leveraging the cone of uncertainty the presentation will also cover techniques for managing management expectations.
You have just received the much desired promotion to Technical Team Lead The team is waiting your direction. You What should you do now?
This session uses discussion to explore common pitfalls encountered by new Technical leads as well as possible solutions.