The Workshop includes a 90 minute kickoff session (conference call or web meeting), a 60 minute follow up session, then a two day requirements gathering workshop on Monday and Tuesday followed by a final half day solution POC solution test drive at the end of the week
I didn’t give this any thought, but then, one day, after I had been working with a different department, doing requirements gathering, and helping “them” solve their issues, I overheard someone say “Mark is our favourite IT person&rdquo
After performing exhaustive technical requirements gathering, employee interviews, and operational observations; a comprehensive RFP was published
The aim of the 1 hour session was to give a little insight into where SharePoint project challenges are and how, through the use of Serious Games techniques, such as Innovation Games(R) and Gamestorming we can break the vicious cycle of poor requirements gathering, unhappy users, SharePoint Celery and conflict between IT and the business teams
The ideal situation would be to solicit feedback, perhaps using social media, to gain insight as to how this customer base would access the information to make a purchase in addition to meeting the regulatory requirements. Requirements gathering in every situation should address as many variations as possible and even if you cannot get it all immediately, there must be a plan in place to address those requirements in an efficient manner
Having spent most of my career working with structured data, I was initially happy to see that the ECM project plan presented at the AIIM ECM Master class, looked a lot like a systems development project plan. Requirements gathering, design, testing, etc., lots of similar tasks
Start with a couple of couple of day long workshops to go over project objectives, scoping and requirements gathering. Use one week sprints, and then aim to produce workable prototypes
And one final reference from a presentation by Bob Lawhorn of CAI in March 2010 about the causes of challenged projects: Poorly defined applications (miscommunication between business and IT) contribute to a 66% project failure rate, costing U.S. businesses at least $30 billion every year (Forrester Research) 60% – 80% of project failures can be attributed directly to poor requirements gathering, analysis, and management (Meta Group) 50% are rolled back out of production (Gartner) 40% of problems are found by end users (Gartner) 25% – 40% of all spending on projects is wasted as a result of re-work (Carnegie Mellon) Up to 80% of budgets are consumed fixing self-inflicted problems (Dynamic Markets Limited 2007 Study) If we agree, for the sake of argument, that the software is not typically the problem, that leaves us with the other two corners of this triangle – the customer or the system integrator
Custom Site Templates Let’s Get Into Dissecting a Successful Engagement and the Method to EPC Group’s Project Methodologies Project Initiation and Planning - Initiation and Definition Activities Once the EPC Group sales and consulting staff has worked with our clients to scope and build the overall proposal and the project has been won, it is time for the Project Management Office (PMO) to start engaging as well as planning the details such as: · Create Work Breakdown Structure · Perform Resource planning · Create Project Schedule · Preparing the Budget · Conduct Schedule Review The EPC Group team now develops the supporting plan definition activities and Project Initiation activities such as the: · Communication and Controlling Procedures · Compile and inspect Project Definition Document · Review and Approve Project Definition Document EPC Group then rolls into our project kickoff sessions \ Preparing for Kickoff Conduct Project Review and Kickoff Processes · Implement EPC Group’s Project Control Documents and our internal Project Server 2010 environment · Kicking of Requirements Gathering o Conduct Initial Requirements Gathering Sessions and Determine Audience o Content Sessions o Conduct Content Requirement Session · Services Sessions o Conduct Services Requirement Session · Equipment Sessions · Conduct Global Equipment Requirement Session · People Sessions · Conduct People Requirement Session · Conduct Global People Requirement Session · Backend Application · Conduct Backend Application Investigation · Steering Committee Sessions · Conduct Steering Committee Member Interviews · Develop Requirements Document · Conduct Requirements Document Review and Apply Updates · Requirements Document Complete Obtain Requirements Document Client Sign Off Requirements Phase End Review Conduct Phase End Assessment - Requirement s Phase End Review Complete Onsite Reviews Conduct 1st - Onsite Review Planning Session Development Environment SharePoint - ORDER HARDWARE & SOFTWARE COMPLETE SharePoint - HARDWARE & SOFTWARE RECEIVED SharePoint - STAGE HARDWARE & SOFTWARE COMPLETE - Provide SharePoint team support in Development Configuration - Provide complete knowledge transfer sessions, build documents, etc
1 Comment - no search term matches found in comments.
” Information Architecture Requirements Gathering Sessions You must be prepared in every SharePoint information gathering session with questions, topics, and agenda items that are relevant to the audience you are interviewing
8403 Colesville Rd #1100Silver Spring, MD 20910USA
Phone: (301) 587-8202Toll free: (800) 477-2446Email: hello@aiim.org
JoinBenefitsLearn More
About UsTerms of Use