Discussion
Pegasystems Inc.
US
Last activity: 2 Nov 2016 17:01 EDT
Project Initiation best practices
I am about to kick off a project initiation phase in a few days for a new project. I remember feeling a little lost on my first Pega project, now having done this a few times, I've definitely fallen into some habits and have a few "go-to" approaches. I thought the topic of best practices and tips for Project Initiation phase would be an excellent 1st post to our new Business Architect community. What better way to get started with the community than to talk about how to get a project started off on the right foot.
Please share your tips to get a Pega project initiated and off in the right direction.
Pegasystems Inc.
US
I would say it’s really depends on the approach and methodology proposed to the client. In my past project experience, I used the following 7 questions:
- Why are we undertaking the project?
- What are we delivering?
- Who is responsible?
- How will the project be delivered?
- When will the project be delivered?
- What are the risks, issues, dependencies and constraints?
After gathering the answers to these questions, I used the Pega provided Project initiation information guide to setup the project.
At the high-level
• Initiate the Application Profile including the following:
- Project Description/Overview
- Business Objectives
- Assumptions/ Risks
- Actors
- Interfaces/Reports
Identify the naming convention for Requirements and Specification including the Pega best practice template
Discuss with team regarding the quality of good user stories ( Ref: Pega Project Initiation Doc)
- Independent?
- Negotiable?
- Valuable?
- Estimable?
- Small?
- Testable?
For additional information, see the attached Pega Project Initiation Document. Hope this helps!