...
- Delivery Goals
- Deliver the Solution
- Integrate the Solution
- Test the Solution
- Implement the Solution
- Outcomes
- Solution and Sprint roadmaps
- Solution Architecture Decisions Log
- Checkpoint Decisions
- Has the solution strategy changed?
- Have the solution resources changed?
- Have the solution objectives and metrics changed?
- Has the solution been validated?
- Have the functional requirements been fully addressed?
- Have the non-functional requirements been fully addressed?
- What adjustments are needed for the solution, the rollout?
- Activities
- if Definition Phase NOT done separately then include the deliverables from that phase here ...
- Definition above
- Design above
- Plan above
- Manage Plan
- Test workships workshops as needed
- Program with Sprints:
- Program planning for Sprints
- Features and Deliverables as Epics, Stories, Bugs, Estimates with Planning Poker,
- Standups on Sprint execution - Sprint cycle ( plan, deliver, test, retro )
- Sprint Demos - functions, designs, tests etc
- Sprint Retros - what was done well ? what can be improved ?
- Define EDC - Engineering Design Change when needed in EDC log
- Define ECR - Engineering Change Requests when needed
- Deliver
- Program phase kickoff / completion planning
- Release plan updates
- Sprint execution - plan, build, demo, review – DOR, DOD
- Project updates
- Test execution and acceptance
- Implement
- Project infrastructure setup
- Solution and test IAM
- Solution and test build setup
- Deployments
- Infrastructure quality checks
...
- TSE - Technical Sales Engineer -
- assess solution needs
- scope deliverable, roles, responsibilities
- assess blockchain need, requirements
- SA - Solution Architect
- solution design - UX, APIs, data services, other services, IAM
- SOW for solution - tasks, deliverables, design concepts
- test specifications
- System Architect
- low level design, details for implementation
- systems integration client, cloud, other
- platform and services integration, deployment, support
- PM
- project definition, management, tracking, plan with WBS
- deliverables, roles, budgets, timelines, risk mitigation
- Agile management
- more
Paramount Project Process Standards
- It will be amazing if all group meetings could comply with proposed time with an emphasis on greater engagement and value creation
- Key outcome/result of the important group meetings to be noted down
- Designs TBD by mutual consensus among Architect,Product Owner and Product Manager
- Any deviation in the implementation from the design needs to be justified and documented to appraise others of the logic driving that change
- JIRA to be embedded as a strategy for product development assessment and better appreciation of the team contribution
- A documented artifact on the individual products will be highly valuable for all the new members to be at sync with the team and start contributing
- A periodic update for appraising Pramod on the works in progress will be excellent
EBC MVP followed all these practices and more
except we did our use cases and stories in GDocs for most of the project before moving to Jira
EBC succeeded because we had key user input continuously.
We ran 1 week sprints normally with 2 user meetings weekly to update designs, review progress.
Rapid Solution Delivery concepts - RSD
...