JavaScript is disabled on your browser. Enable JavaScript to use this site. Learn more

Structural Enabling Conditions 2

Add to Favourites

Post to:

Comments

Presentation Transcript

Case Study : CKW Community Knowledge Worker A network of CKWs, receiving training in information delivery and data collection, to use mobile technology to take agricultural extension services to the most remote and poorest farmers, and help them to escape poverty. Case Study (c) 2010 Institute of Mobile Technologies

Project Types : Project Types Increasing Project Complexity

Software Capability Maturity ModelSW-CMM : Software Capability Maturity ModelSW-CMM

Organizational Strcuture : Matrix Structure Organizational Strcuture

Organizational Culture : Organizational Culture

Project Management Methodologies : Project Management Methodologies Adaptive Project Framework Agile Software Development Crystal Methods Dynamic Systems Development Model (DSDM) Extreme Programming (XP) Feature Driven Development (FDD) Information Technology Infrastructure Library (ITIL) Joint Application Development (JAD) Lean Development (LD) PRINCE2 PM Knowledge of Body Rapid Application Development (RAD) Rational Unified Process (RUP) Scrum Spiral Systems Development Life Cycle (SDLC) TenStep Project Management Process Waterfall (a.k.a. Traditional)

Some PM Tools/software : Some PM Tools/software Your notebook? MS Word? MS Excel MS Project – Standalone Version MS Project – Server Version Jira suite Artemis Views Open Plan Cobra Primavera Etc.

Challenges with Stand-alone PM Tools : Data gathering is an intensive Creating tasks and sub-tasks is not dynamic enough Updates are not real-time Visibility to other team members progress is minimum; often too late to notice delays Impossible to generate cross-dimension report Not an easy way to calculate total man/hour needed to finish the task unless going through intensive data gathering and analysis Hard to get combined reports on tasks/features-components Track of what was done when and what is scheduled for when is not easy and time consuming Challenges with Stand-alone PM Tools

Stand-Alone vs. Team Oriented Tools Comparison : Stand-Alone vs. Team Oriented Tools Comparison

Highlights of Web-based PM Tools : Create tasks/ sub-tasks, report bugs, issues, request for change, maintaining back logs by all team members and stakeholders. Multiple projects and tracks can be defined by appropriate access model: Task takers Managers Other stakeholders Tracking resource assignment to the tasks is easy Project status can be visualized in real-time per different criteria: Tasks Done, in Progress, To Do Workload per resource Size of each components and task Measuring impact of changes on project is easier Affected versions per task is visible Labels, themes and epics can be associated with the tasks Highlights of Web-based PM Tools

Web-based PM Tool : Web-based PM Tool

Social-Oriented PM Tools : The software is web-based and/or accessible on network Project information and related tasks are combined under one tools/database It can be integrated to other productivity tools such as documentation repository, code repository, etc. Social-Oriented PM Tools

Social Networks for Enterprise : It is a growing trend to use social-networks for enterprise internally Examples: Chatter for Salesforce (a Twitter type component), Confluence for Atlassian (A wiki tool for JIRA suite, Yammer, etc.) Social Networks for Enterprise

Communication Protocols : Communication Protocols

Documentation Standard : Requirements Business Usecases Technical Documents Architecture Database APIs Test Cases/Test Plans Etc. Deployment manual Post Deployment Reports Documentation Standard

Sample Business Usecase : Sample Business Usecase

Social Context: Open-Source Paradigm : open-source is software for which the source code is distributed and accessible via the Internet without charge or limitations on modifications and future distribution by third parties. Common characteristics of Open Source: E-Learning Community Building Self-Driven Interactive Environment Almost exclusively administered online Etc. (c) 2010 Institute of Mobile Technologies Social Context: Open-Source Paradigm

Social Aspect of Open-Source : Team Members are Active Participants not Passive Learners Adopting Open-Source Technology sets the paradigm from “understanding an existing tool and become technicians to deploy it” to “Asking the question of what is needed and how can ‘we’ build it”. Social Aspect of Open-Source

Enabling Environment : Following characteristics can be extracted about an enabling environment from various studies: A shared space that fosters emerging relationships is an enabling context. Such environment can be physical, virtual, mental or all three. Think of an enabling environment as a place in which knowledge is shared, created, and used. In this sense, an enabling environment does not necessarily mean a physical space. Rather, it combines aspects of physical space (such as the design of an office or dispersed business operations), virtual space (email, intranets, teleconferences), and mental space (shared experiences, ideas, emotions). More than anything, it is a network of interactions, determined by the care and trust of participants. Enabling Environment

Enabling Structural Conditions for Technology Competence : Enabling Structural Conditions for Technology Competence Enabling Structural Conditions for Technology Competence Framework © 2010 Shayan Mashatian