Research Objectives: Develop an IT 2.0 adoption model to assist managers of IT / IS projects in the treatment of lessons learned; Validate the model proposed by reviewing the model with experts of project area.

1. Lessons Learned Model for Projects
Supported by Web 2.0 Tools: a Mixed
Methods Approach
Debora Virginio Rosa – deborenhas@gmail.com
Marcirio Silveira Chaves – mschaves@gmail.com
Mirian Oliveira – PUCRS - miriano@pucrs.br
CNPQ Project: 408117/2013-3

2. INTRODUCTION
1
→ Actually project
review are in practice in
more than 90% of
organizations but they’re
not using eletronic
format (Standish Group,
2013)
→ Collaborative tools
with mechanisms and
features that make
lessons learned
processes easier and are
being initiated in project
management context -
PM 2.0 (Sinclair, 2007; Levy,
2009; Shang et al., 2011;
Palacios-Marqués et al., 2013)
→ Tacit knowledge held in project
members minds (Carrillo, Ruikar, & Fuller, 2013)
→ Difficults in capture knowledge during
the project due to activities priorization
and lack of time (Swan, Scarbrough, & Newell,
2010)
→ Experiences and knowledege, when
capture during the project are not
integrated into the organization
knowledge base (Pemsel & Wiewiora, 2013;
Duffield & Whitty, 2014)
→ Knowledge Management Systems are
inefficient:
• Limited tools due to search restrictions
(Weber et al.,2001)
• Difficult on finding data, and when data
is found the information provided has
limitations – incomplete data (Swan et. al,
2010)
Justification
Problems

3. TARGET 2.0 PRELIMINARY MODEL
2
Theoretical Background
• People: Situated Learning Theory,
Mutual Care Theory, Social Aspects,
Knowledge Management
• Process: Lessons learned methods,
lessons learned processes, project
learning framework, knowledge
management model for projects,
project management methodology
• Technology: IT 2.0 tools such as
social network, blogs, wikis, cloud
tools

4. RESEARCH DESIGN
3
Research Objectives
 Develop an IT 2.0 adoption model to assist managers of IT / IS projects in the
treatment of lessons learned;
 Validate the model proposed by reviewing the model with experts of project area.
Research Design
 Exploratory research
 Mixed Methods: Partially mixed concurrent equal status design (Leech and Onwuegbuzie,
2009)
 Portuguese / English Questionnaire (183 answers) + 10 in depth interview with
member projects (average 12 years experience in projects)

5. ANALISYS RESULT – Project Management
4
What lessons learned processes do you consider important at each phase of a project?
Raise Awareness  Initiating
Collect  Executing / Implementation
Verify  Control
Store  Closing
Disseminate  Closing
Reuse  Executing / Implementation
Initiating
• Raise
Awareness
• Reuse
• Collect
• Verify
• Disseminate
• Store
Planning
• Reuse
• Collect
• Verify
• Raise
Awareness
• Disseminate
• Store
Control
• Verify
• Store
• Collect
• Reuse
• Disseminate
• Raise
Awareness
Executing/
Implementation
• Reuse
• Store
• Collect
• Verify
• Disseminate
• Raise
Awareness
Closing
• Store
• Disseminate
• Collect
• Verify
• Raise
Awareness
• Reuse

6. ANALISYS RESULT – IT 2.0
5
Social Media
VoIP
Cloud Store/Share
Cloud Editing Tool
Blogs
Wikis
Mashups
Microblogs
RSS
Tags
Wikis
Social Media
Blogs
RSS
Cloud Editing Tool
Cloud Store/Share
Tat
Mashups
Microblogs
VoIP
QUALI QUANTI

7. ANALISYS RESULT – Lessons Leaarned
6
QUALI QUANTI
Raise Awareness
Collect
Store
Disseminate
Verify
Reuse
--
Raise Awareness
Collect
Store
Disseminate
Verify
Reuse

8. ANALISYS RESULT – Propositions
7
P1
• Knowledge management in IS/IT projects assists the realization of the
project. (YES)
P2
• The project team influences the knowledge management, and so, the results
in IS/IT projects. (YES)
P3
• IT 2.0 are used in the organization and by the project team.(PARTIALLY)
P4
• IT 2.0 can assist in the process of managing LL in IS/IT projects. (YES)
P5
• The project team should be mobilized and encouraged to carry out the
processes of lessons learned management in IS/IT projects. (YES)

9. ANALISYS RESULT – Meta-inferences
8
Bridging
• Lessons learned management
underachieved in projects
• Processes rarely used in projects
(questionnaire) and modifications
were suggested in interviews
(Verify, Disseminate processes)
• Difficulties in measuring
effectiveness of the reuse process
• Lessons learned processes by
project phase
• Web 2.0 tools considered effective
for lessons learned management
Bracketing
• Raising awareness processes and
organization guidelines
• Project Management Methodology:
traditional method versus agile
method
• Recommended tools to perform
lessons learned management

10. 9
DISCUSSION – Target 2.0 Final Model

11. 10
CONTRIBUTIONS
*** Theory
 Type of theoretical contribution:
 Explanation and Prediction (Gregor, 2006)
 Dimensions of theoretical contribution:
 Originality: Incremental
 Utility: Practical and Scientific (Corley e Gioia, 2011)
 Theoretical contribution to lessons learned management (processes)
*** Practice
 Target 2.0 model assists IT/IS project members:
 Everyday tools
• Knowledge retention
• Not affected by turnover

12. 11
CONCLUSION
* Lessons Learned can be managed in IT/IS projects in any project phase
with the support of IT 2.0 tools as suggested in Target 2.0 model
Processes People Technology
Limitation
• Organizations using lessons learned
supported by IT 2.0 tools
• Raise Awareness processes vs available
tool
• Lack of evidence of successfull
experiences in lessons learned
management
Futurework
• Agile Methodology
• Model test/application
• Reuse process

13. • Managing Web 2.0 Technologies in Projects - TiP 2.0
Research Group
http://tip20.wikidot.com