The Kids Project supports the management activities of a nursery. In this project, I was project manager of a group formed by 15 developers. In these slides report the progress of the project and my lesson learned.
5. The Kids Project
Size Cosmic
System
Functional Size
Entry Size Exit Size Read Size Write Size
419 103 204 48 64
143 40 62 20 21
Size of Service Management subsystem
sabato 28 settembre 13
6. The Kids Project
TUCP_CP1 CP1 TUCP_CP2 CP2 TCF
1096 778.16 1098 779.58 0.71
Size Class Point
sabato 28 settembre 13
7. The Kids Project
TUCP_CP1 CP1 TUCP_CP2 CP2 TCF
1096 778.16 1098 779.58 0.71
364 225.68 364 225.68 0.62
Size of Service Management subsystem
Size Class Point
sabato 28 settembre 13
8. Team composition
Ideal team
1 Web Designer
2 experts in JSP/Servlet
2 software analysts
3Task Oriented
2 Interaction Oriented
sabato 28 settembre 13
9. Team composition
Real team
0 Web Designer
0 experts in JSP/Servlet
0 software analysts
4Task Oriented
1 Interaction Oriented
sabato 28 settembre 13
12. Management goals
All functionalities of the subsystem
must be implemented!
Quality must be high!
Team must be motivated always!
sabato 28 settembre 13
13. Kids lifecycle
Spiral model
Spiral model is risk driven
Possibility of customizing
every cycle of spiral
In the end, our approach is very similar to Waterfall
Lifecycle but...
sabato 28 settembre 13
25. Kids results - RAD
It’s arrived to the 4.0 version
sabato 28 settembre 13
26. Kids results - RAD
It’s arrived to the 4.0 version
It’s was subjected to a three good
review (13/24 item in the checklist
as mean)
sabato 28 settembre 13
27. Kids results - RAD
It’s arrived to the 4.0 version
It’s was subjected to a three good
review (13/24 item in the checklist
as mean)
RAD is consistent with the
implementation!
sabato 28 settembre 13
42. Kids results - ODD
It’s arrived to the 2.0 version
sabato 28 settembre 13
43. Kids results - ODD
It’s arrived to the 2.0 version
It’s was subjected to a bad
review...the document was not
complete!
sabato 28 settembre 13
44. Kids results - ODD
It’s arrived to the 2.0 version
It’s was subjected to a bad
review...the document was not
complete!
Although the revision was not
perfect, the document is consistent
with the implementation
sabato 28 settembre 13
52. “You must take the compromise to win,
or else nothing.”
Ayrton Senna
sabato 28 settembre 13
53. Earned Value of... quality
Project quality state:
sabato 28 settembre 13
54. Quality PRO
Presence of design
patterns increments the
quality of Kids
What is the consequence?
Maintainers will be grateful of our quality strategy
on the code!
sabato 28 settembre 13
55. Quality PRO
What is the consequence?
Maintainers will be grateful of our quality strategy
on the code!
LCOM: 0.341
Efferent Coupling: 3.588
WMC: 26.083
sabato 28 settembre 13
56. JU
Unit testing of all Kids components
Integration testing of all Kids
components
Quality PRO
# test cases: 53
# test classes: 12
# test cases: 162
# test classes: 32
Service Subsystem Kids
sabato 28 settembre 13
57. Quality CON
There is alignment of the
documentation to the code
but...
the quality of artifacts of high level
design could be better...
sabato 28 settembre 13
58. Quality CON
Some checklists could be
more accurate
This problem could be mitigated
with more training on the
software inspection...
sabato 28 settembre 13
60. “All management is people management.”
“A company is only as good as the people it
keeps.”
“The only way to get people to like working hard
is to motivate them. Today, people must
understand why they're working hard. Every
individual in an organization is motivated by
something different.”
sabato 28 settembre 13
61. There’s an huge impact of
people management on
the success of a project
Impact of People Management Practices on Business
Performance [Patterson et al.]
The impact of strategical human resource management on
Organizational Performance [Caliskan]
MOTIVATION
sabato 28 settembre 13
62. Listen, listen,
listen...
Rethink, review,
and reward
Be fair
Be flexible
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
Include your
team in key
management
decisions
MOTIVATION
sabato 28 settembre 13
63. Listen, listen,
listen...
Rethink, review,
and reward
Be fair
Be flexible
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
Include your
team in key
management
decisions
MOTIVATION
sabato 28 settembre 13
64. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
65. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
66. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
67. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
68. Number of meetings: 13
Average duration: 58.84 min
Average frequency: 1/4.81 days
MEETINGS E COMMUNICATION
sabato 28 settembre 13
71. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
72. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
73. Listen, listen,
listen...
Rethink, review,
and reward
Be flexible
Be fair
Focus only on
solutions and not
on problems
Rid your mind of the
word “manager” and
replace it with
“leader”
Scorn in private,
praise in public
MOTIVATION
Include your
team in key
management
decisions
sabato 28 settembre 13
76. RESUMING...
67 days of work
19 documents released
(12 of management)
Overall, we obtain a good
quality
Overall, good management
of people
sabato 28 settembre 13
77. RESUMING...
67 days of work
19 documents released
(12 of management)
Overall, we obtain a good
quality
Overall, good management
of people
And what about cost of project?
sabato 28 settembre 13
80. Requirements analysis has been carried out too long!
Fear of the client!
Why?
A lot of requirements and
low time available
There wasn't an existing
system
WHAT WERE THE MAIN PROBLEM?
sabato 28 settembre 13
81. THE PROBLEM...
The problem is not the change itself, because the
changes will take place, the problem is an inability to
cope with the changes when they occur.”
Kent Beck
"Everything changes in the software.
Requirements change.
The design changes.
The commercial aspects change.
Technology changes.
The team members change.
sabato 28 settembre 13
82. HOW COULD THE
PROBLEM BE SOLVED?
The client must be part of software development!
sabato 28 settembre 13
83. HOW COULD THE
PROBLEM BE SOLVED?
The client must be part of software development!
AGILE SOFTWAREDEVELOPMENT???
sabato 28 settembre 13
84. The Golden Hammer does not exists!
LESSON LEARNED
Be Open Minds!
sabato 28 settembre 13
85. WHAT WAS THE
BIGGEST
OBSTACLE TO THE
SUCCESS OF
PROJECT?
For some team members,
the documentation...
sabato 28 settembre 13
86. When the documentation supports software
development?
When it helps the developer to
understand the problem domain
When it helps the developer to
understand the design choises
When it helps the developer in
the maintenance phase
When the developer is not afraid
of documentation!
but, also...
sabato 28 settembre 13
87. 0 10 20 35 45 ...
Percentage of documentation
Understanding
High
Medium
Maybe, the same rule on the percentage of comments in the code
can be applied in the documentation...
sabato 28 settembre 13
89. WHAT LED US TO SUCCESS?
Cohesion of team
Clarity of management goals
Training: every time, everywhere
Work, work, work...no unnecessary words!
Good resource management
sabato 28 settembre 13
90. The first stable version of Kids the 21/12/2012:
In the our ideas, this will be the whole tested system
YES, WE CAN!
WHAT LED US TO SUCCESS?
Do you remember this slide?
“‘Yes, we can’ does not want to express an attempt, but a
tenacious willingness and determination to get to the bottom.
We can get to the bottom because we know how do.”
sabato 28 settembre 13
91. WOULD YOU DO A SIMILAR
EXPERIENCE?
Doubtless, yes...
sabato 28 settembre 13
92. WOULD YOU DO A SIMILAR
EXPERIENCE?
Doubtless, yes...
And...what about me?
sabato 28 settembre 13
93. WOULD YOU DO A SIMILAR
EXPERIENCE?
Doubtless, yes...
And...what about me?
NO, THANKS.
sabato 28 settembre 13