What creative and technical skills are essential to have on your intranet development team? This matrix lays them out in quantitative and qualitative terms and lets you assess how a candidate stacks up.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Deliverable Templates Project Plans Checklists Presentations|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
72 items found
You already know the benefits of creating an Intranet. Justify it with a solid business strategy plan.
Database management begins with SQL. If you're starting to use relational databases, you'll have to learn this standard language. Here's where to begin.
If you want to extend your SQL capabilities with Oracle's PL/SQL option, this is a good place to get a solid footing.
Based on an introductory course on the principles and concepts of project management, this collection of presentations cover the definition of a project, what makes a project successful and how projects can go wrong. It covers the following areas of a project: planning, initiating, controlling and ending.
Introduction to Strengths-Based Project Management - Finding Your Strengths (Part 1): Supporting Materials Package
This zip file contains three PDFs in support of the webinar Introduction to Strengths-Based Project Management - Finding Your Strengths (Part 1). It includes a character strengths checklist; a classification of character strengths and virtues; and a PDF of slides with a section to take notes during the presentation.
Introduction to Strengths-Based Project Management - Seeing the Strengths of Others (Part 2): Supporting Materials Package
This zip file contains two PDFs in support of the webinar Introduction to Strengths-Based Project Management - Finding Your Strengths (Part 2). It includes a classification of character strengths and virtues; and a PDF of slides with a section to take notes during the presentation.
The following form provides a mechanism to document and track any issue during its life cycle. After an issue is created, a team should determine whether the issue has any bearing on the project and what should be the course action to address the issue. All issues must be periodically reviewed to determine if they still have any significance for the project.
This document can be used to keep track of any issues that arise during the project. It is advisable to keep track of such issues, especially if they can not be solved quickly, or if many issues arise in a short time. Also, it is recommendable not to remove any documented issues once they are solved.
The issue management process is fundamental to the successful delivery of the project. It ensures that each issue identified within the project environment is documented, prioritized and resolved within an appropriate timeframe. Use this document as a framework to identify, document, prioritize and resolve your project's issues.