3. Origin of the idea
• Welcome to our 10x delivery innovation model.
Here is the quick overview of our big idea - In this
idea, we want to focus more on methodology than
process automation. We plan to propose the idea
with 6 project stages for easy understanding of our
10x delivery mechanism, hence controllable and
uncontrollable factors are clubbed in each phase of
the project which provides predictable result and
generate, reliable insights based on the data
collected during the project execution.
4. Fool Proof
Initially let`s define what is 10X
delivery innovation by the below
statement.
• To provide the sense of control and
flexibility to the delivery team by
enabling them with past project
experience / Risk involved during
architectural decision making lastly
provide transparency and control in
co-creation with clients on the value
delivery.
5. Methodology to define the Problem space
To proceed further we thought understanding the Problem space may help
us to define the success criteria:
• From the developer perspective, the burning problem is Understanding the
vision and scope which highlights on what is the project`s key scope and
what are value additions (or secondary derivatives) which defines the road
map. From the Client perspective, they feel SAP is overpowering many
places by being a closed environment were customer have very less control
what is being delivered to them.
• The core idea can be staged as 6 vital procedures to be considered as a
methodological approach for 10X delivery.
• Different project players were Interviewed (25 project owners and leads)
6. Innovations Given dedicated time for teams to encourage collective learning
By quick failing to identify risk and bottle necks in the project.
7. Virtual project assistant
• In order to increase the team`s delivery efficiency we went back in history
and analyzed data with different project managers and tried to sense a few
critical factors which can influence the team`s performance. After a deep
interaction and synthesis with different teams, we have come up with a
structure for 10X project delivery system as structured below.
• In every project the success of a team is majorly measured by its timely
delivery, Quality of delivery and the way it is delivered.
• The team`s smartness can be defined by the clarity they gain on the
business requirement, control over the user experience expectation,
technology/framework utilization
• Enablement of Project Management: Dashboard assistance with MRS
implimentation for Well informed data-driven decision-making capacity
does not burn out by overworking and over-engineering .
9. Smart Team space
Project Camps setup for quick collective learning: Fail fast approach.
• Simple Vision and scope tool which can populate content based on the deep learning
concept and create simulated content which can have images and videos for easy
visualization.
• Take pivotal decisions by connecting with project reviewer: 3rd eye point of view (Some
one who can provide the bigger picture who can share opinion holistically in terms of
value delivery proposition)
• Collective experience learning which improves confidence : Improves Team`s
commitment than individual`s commitment (Like Scrum updates which focus majorly on
individuals update instead this methodology focus on value delivered as a team).
• Utilize time by automating regular project tasks: Efficient reusable artifacts as plugins
which requires zero or less coding as a package which includes gateway services and
interfaces predefined which are flexible enough.
• Transparency and Control. Team`s day to day activities are transparently listed/ showed
to the clients on which they can comment and appreciate the value or provide direction.
11. The Problem space
• From the developer perspective, the burning problem is
Understanding the vision and scope which highlights on what is the
project`s key scope and what are value additions (or secondary
derivatives) which defines the road map. From the Client perspective,
they feel SAP is overpowering many places by being a closed
environment were customer have very less control what is being
delivered to them.
• Not transparent some times
12. Easy decision making – Data Driven
• Project Camps setup for quick collective learning: Fail fast approach.
• Simple Vision and scope tool which can populate content based on
the deep learning concept and create simulated content which can
have images and videos for easy visualization.
• Take pivotal decisions by connecting with project reviewer: 3rd eye
point of view (Some one who can provide the bigger picture who can
share opinion holistically in terms of value delivery proposition)
• Collective experience learning which improves confidence : Improves
Team`s commitment than individual`s commitment (Like Scrum
updates which focus majorly on individuals update instead this
methodology focus on value delivered as a team).
13. Benefits
• Utilize time by automating regular project tasks: Efficient reusable
artifacts as plugins which requires zero or less coding as a package
which includes gateway services and interfaces predefined which are
flexible enough.
• Transparency and Control. Team`s day to day activities are
transparently listed/ showed to the clients on which they can
comment and appreciate the value or provide direction.
14. 3rd Eye Perspective The project manager and architect can involve external
Domain experts for adding additional perspective.
15. Do your customer need more time to make decisions?
During customer workshops specific requirements are not
frozen for longer duration and handling this can become more
complex due to interdependency. Also it is felt that there are
visible trends in next generation customers who look for more
control and transparency during the development phase.
Help them to understand and do not assume you are the best
Understood. The key is to Keep the feedback loop shorter.
16. Project Camps Develop collective knowledge by failing fast as initial
project camp methodology.