Research Triangle Software Symposium - June 20 - 22, 2008 - No Fluff Just Stuff

Mark Johnson

Research Triangle Software Symposium

Raleigh · June 20 - 22, 2008

You are viewing details from a past event
Mark Johnson

Director Consulting @ Hortonworks

Mark Johnson is a Director of Consulting at Hortonworks where his day is spent helping people achieve value from their Big and complex Data repositories. Mark has worked on a wide range of technology during his career. Most recently he has focused on the Hadoop ecosystem. 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.

Presentations

Software Development Risk Analysis techniques

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. Reasons for a project failure will vary based on the stakeholder interviewed. This session will provide a software development risk framework and examples you can apply in your projects to reduce or at least soften the impact of failure.

Getting to Acceptance: Validating your requirements with FitNesse

How do you know when you are “DONE” and the assignment is complete? Well of course you are done when your requirements are complete. But it always happens that your interpretation differs from the customer/management's interpretation.

Promoted to Technical Lead. Now what do I do?

You have just received the much desired promotion to Technical Team Lead The team is waiting your direction. You What should you do now?

Software Project Estimation

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.