If the tools and technologies that support business analysis initiatives are so good, why do we continue to see so many project failures? Is it the failure of business analysts, is it a lack of training and/or certification or is it that customers don’t understand what they want? No matter how much marketing hype there is around frameworks like Lean Six Sigma, TOGAF, PRINCE2 and Agile (to name a few), there is no silver bullet. It takes hard work, knowledge, education and a good dose of common sense to ferret out the things that you and your customer didn’t know you didn’t know.
Projects fail because of what you didn’t do at all, rather than what you didn’t do well. This session looks at how you might identify and model the requirements for a process modelling tool as an aid to understanding how complex even a supposedly simple application can be.
Peter Stanford – Managing Director of Artefaction Pty Ltd
Peter has an extensive and varied background in business and IT covering Technical, Sales, Marketing, General Management, University lecturer in computing-related subjects. Master of Computing (Software Engineering) and author of “Practical System Development – a Project-Based Approach”. Application Development in both Windows Forms and ASP.NET, MVC, CodeFluent Entities and Telerik UI controls.
His specialties include General Management, Marketing, Technical Consulting, Enterprise and Application Architecture, Business Process Modeling, Solution Architecture, Database Architecture and Design, User Interface Design and Project Management.