The document outlines a project management framework that emphasizes efficiency, quality, flexibility, and communication in web software development. It advocates for a multidimensional approach, using agile principles to maximize ROI while promoting collaboration among clients and teams. It highlights the importance of understanding client expectations, maintaining open communication, and adapting project methodologies to fit specific contexts.

1. Project Management Framework
A 2D pattern approach to web software development

2. Basic
Observations
TBSCG is a group of professionals, each with their own unique
background, beliefs and practices, but all sharing a single mantra:
Efficiency & quality for maximum customer satisfaction
Our clients are a community of professionals, each with their own
culture, objectives and constraints, but all sharing a single expectation:
Flexibility and performance to generate the best possible ROI
Challenge 2 3 4 5 6 7

3. 1 Foundation3 4 5 6 7
Deliver with
respect

4. We filter our client’s
expectations through
our core values prism
Flexibility +Performance + Quality + Collaboration
Embrace change
Open and honest communication
Multiple models
Maximize ROI
Assume simplicity
Rapid feedback and prepare the next step
Listen with concern
Model with a purpose
Fair relations
ThankstotheinspirationofJohnWileyandhisAgileModeling
1 Foundation 3 4 5 6 7

5. Values of
objectivity
Assume simplicity, accept incremental change, keep your
focus, model with purpose
Remember what the initial idea was: why are you doing the
task in hand?
Think about which gear is actually needed to make your
journey. Having a big suitcase doesn’t automatically mean
that you have to travel with your entire wardrobe.
Don’t expect an all-encompassing model from the start.
Remember that you will learn from your initial choices.
1 Foundation 3 4 5 6 7

6. Values of
efficiency
Maximize ROI, multiple models, rapid feedback
Share the same goals and support one other.
Resolve situations that sap your time and energy.
Choose the right tool for the right job.
Don’t use all the colors just because you have them on your
palette.
Make sure you are on the right track.
Guarantee a common understanding
1 Foundation 3 4 5 6 7

7. Values of
openness
Embrace change, prepare the next step, open
communication
The same tool in a different context can generate new
results.
Demonstrate agility with the product, the method, the
organization.
There’s always somebody that will use your product, and
somebody that will maintain your software.
When you are playing the software development game
your secondary goal is to setup to play the next game
(Alistair Cockburn, Agile’s father)
Listen carefully and respect other people's constraints
1 Foundation 3 4 5 6 7

8. Values of honesty
Listen with concern, honest communication, fair relations
The requester has a good reason for making his request.
Understand the expectations, think about the benefits.
Remember, you are involved in a collaborative game with a
shared objective.
1 Foundation 3 4 5 6 7

9. A
multidimensiona
l framework with
values
1 2 Dimensions 4 5 6 7

10. Multiple
dimensions
The professional relationship we want to forge with our
clients is multi-layered
Company 2 Company
Team 2 Team
Individual 2 Individual
Our observations:
Each layer has its own set of standards
A software development process must be part of a
broader business commitment.
1 2 Dimensions 4 5 6 7

11. 2-level approach
Build a cooperation framework
Company commitment
PMI-influenced
Clear milestones
Guarantee a fast delivery and setup
Reusable pattern
Light execution
Agility
1 2 Dimensions 4 5 6 7

12. Multiple models
1 2 3 Methods 5 6 7

13. Our observations
Knowledge accessibility, Do-It-Yourself attitudes, and
product-oriented marketing have led everyone to think
solution before needs.
Methodologies and organizations are deeply linked.
Agile methods demand mature relationships between
business and IT.
Enterprise governance policies demand structured and
uniform project reporting.
Enterprise processes need to match on certain points.
Profound shifts don’t happen overnight in corporate
organizations.
1 2 3 Methods 5 6 7

14. Are there really
only 2 models?
WATERFALL
Rigid
Old fashioned
Heavy
Boring
Ignorant
Complex
IT-oriented
Brick & Mortar
AGILE
Flexible
Trendy
Light
Fun
Clever
Easy
Business-oriented
2.0
1 2 3 Methods 5 6 7
? ?
Is it that
simplistic?

15. Our project
approach:
One method for
each dimension

16. Co-operation
framework
1 2 3 4 Control 6 7

17. Build Co-
operation
For first-time projects
For a one-shot project
For program management &
portfolio layers
For specific requests
Clear Milestones
Controlled follow-up
Broad communication
Learn together in confidence
1 2 3 4 Control 6 7

18. A waterfall in clear
water
Initiation to guarantee a shared
understanding
Planning to reach an agreement
on scope and timing
Controlled & Monitored
execution with open
communication & fast feedback
Closure to assess lessons learned
and review the next step
1 2 3 4 Control 6 7

19. Collection of
deliverables
Kick-Off
Engagement framework
Project Statement Of Work
Functional contract, Solution
design & Detailed planning
Monitoring reviews
Issue tracking with JIRA
Product evaluation
Project closure
1 2 3 4 Control 6 7

20. Fast Delivery
framework
1 2 3 4 5 Agility 7

21. Package
contracts
In a mature working relationship
with the client
For clear demands with agreed
commitments
For local delivery within the
framework of wide rollout plans
(multi-country, multi-division)
Iterative development
Agile organization
Short cycles
1 2 3 4 5 Agility 7

22. Iterative cycles
Inception to define high-level
requirements & engagement
Elaboration using the iteration
plan
Execution involving strong
collaboration
Transition to review delivery and
accept
Ongoing assessment for strategy
assurance and scope refinement
1 2 3 4 5 Agility 7

23. Light & Agile
Organization
One Project “Master”
One Product Owner (client or rep)
One Technical Owner (lead
developer)
Initial contract (Statement Of
Work)
Online follow-up (JIRA)
Evaluation reviews
Final closure
1 2 3 4 5 Agility 7

24. Framework
combinations
1 2 3 4 5 6 Combine

25. Program
management for
enterprise CMS
At the program level
Corporate strategy
Resource management
Enterprise platform
For new websites / cooperative projects (with other teams)
Initiation with a clear baseline, RACI, planning
Controlled delivery plan with dependencies
Mutual Commitment
For ongoing enhancements, later phases
Small team, short development cycles
Fast feedback, evaluation & validation
1 2 3 4 5 6 Combine

26. International DAM
rollout
Corporate strategy definition
Program planning with corporate project governance
Overall assessments
Project roadmap
For the initial setup
Architecture definition
Waterfall planning
Delivery of a vanilla setup with out-of-the-box features
Validation and roadmap review
Regional roll-out
Small teams, short development cycles
Continual reporting to the central program governance team for
product management and enterprise adoption
1 2 3 4 5 6 Combine

27. Let’s combine
together!www.TBSCG.c
om
LONDON (uk) - PARIS (fr) - BRUSSELS (be) -
WROCLAW (pl) – BARCELONA (es) - TAMPA
(fl-usa)