USA: +1(669)289-8683 
Sign in
Assignment requirements This assignment follows on from the previous Social Media Research Center assignment case study. Now that the project sponsor has approved your Project Charter and associated documents, you may proceed to the planning phase of the project by providing a formal project report for the project sponsor based on the following project planning documents. You may make any appropriate assumptions needed to enable the successful completion of the project.Gantt chart and Critical Path Diagram Budget Risk Register RACI ChartStakeholder Communications Plan RationaleThis assessment item builds on theoretical knowledge already gained.This assignment provides you with the opportunity to demonstrate that you are able to: • describe the key elements of the IT project management framework, including project stakeholders, the project management knowledge areas, common tools and techniques, and project success factors; • describe the role of IT project management as part of a profession, from the viewpoint of the practitioner as a member/leader of the project team; • explain the relation of the Project Management Body of Knowledge (PMBOK) guidelines to successful project management; • appreciate how IT project management begins with development of a good business case in the project charter, in order to produce effective, efficient and quality IT project outcomes on time and within budget; • demonstrate how a practicing IT project manager actually applies disciplined IT project management techniques, project management skills, methods, techniques and software tools in the IT industry.demonstrate how a practicing IT project manager actually applies disciplined IT project management techniques, project management skills, methods, techniques and software tools in the IT industry. Marking criteriaGantt chart and Critical Path Diagram (20 marks)Budget (20 marks)Risk Register (10 marks)RACI Chart (10 marks)Stakeholder Communications Plan (10 marks)Correct in-text referencing; reference list; report format; overall presentation (10 marks)
Time+Management (2).ppt
CharlesSturt University
Subject:
Information Technology Project Management (ITC493)
Assignment item: 2
Professor:
Chandana Penatiyana Withanage
Student: Mirza
Raza
Ali Khan
Student ID:
115290606
Introduction
Social media has been the most happening trend in the world of the internet, where it continues to show how powerful it can be in voicing people’s opinions, which was not as easy to do previously and certainly couldn’t be done for such a large audience, in such a quick and efficient manner.
The University, has identified that the best step forward for its growth is to build a research centre to carry out research in the area of social media. In this way, the university can leverage this increasingly powerful trend of social media to build its reputation as a quality research provider and also to tap into the students who are interested in the field of social media. Complimenting these efforts, it becomes essential for the research project to have a good website, in order to promote its research studies on social media platforms. The unit however, does not have a great deal of experience carrying out research in the area and also, the IT department of the university is not specialized to handle the website project on its own. Therefore,
Bruce
the project manager for the research centre has appointed me to manage the website project and also to provide a Strengths, Weaknesses, Opportunities and Threats (SWOT) analysis, which can further help in understanding the implications of undertaking a project of this nature.
This first part of this project report discusses the SWOT analysis of the social media research centre project, providing an analysis of the factors crucial to be considered and accounted for.
The report continues to show how the website project can be implemented, in the following steps (Heiyanthuduwage, 2013, p. 1):
· Project charter for the Center Website Project.
· WBS for the Center Website Project.
· Stakeholder Register and Stakeholder Management Strategy for the Centre Website Project.
· Milestone Report for the initiating and planning processes for the Centre Website Project.
SWOT Analysis
|
Strength |
Weakness |
|
1. Ease of staff in handling the change in nature of work as several staff are already involved in research in the area. 2. It is the most appropriate and viable research area, as identified by thorough analysis with several consultants. 3. Potential for Bruce and his staff to grow and further develop their research skills. 4. Good guidance and an experienced outside perspective as the international expert in research in the area has offered his expertise to Bruce. 5. Research in the area can benefit the university in better handling its own social media initiatives. 6. High support from senior executives for the project. |
1. Tremendous pressure from the senior executives, to carryout high quality and focussed research. 2. Lack of experience and reputation of the staff in providing scholarly research output. 3. Increase in the workload of employees, may affect their overall performance in other tasks. 4. High pressure from senior executives for results may lead to high pressure on staff, affecting work quality/productivity. 5. Frustration among staff due to the continuous need to learn as technology and trends evolve. 6. Credibility of the research may be a question as the university is not known well to provide quality research output. |
|
Opportunity |
Threats |
|
1. High market share due to the associated centre ceasing its operations. 2. Increased students could enrol in the university due to the existing demand from Master’s and Doctoral students for programs in the area. 3. High public interest and involvement in research in the area, due to the nature of the industry. 4. Interest of media in the area would lead to increased media exposure for the university. 5. Opportunities to collaborate with other research centres doing research in the area. |
1. High volatility in the social media industry due to rapid changes in trends in the social media due to changes in technology. 2. Research in this area demands for a high adaptability to change in order to keep pace with the constantly changing world of social media. 3. Errors or mistakes in the research may prove costly as they could lead to widespread criticism in the media, which may lead to negative publicity and affect the image of the university itself. 4. Student may choose not to enrol due to instability/changes. 5. Social media security threats existing today, can lead to a fall in demand for social networking |
Project Charter
A project charter is a document that formally recognizes the existence of a project and provides a summary of the project’s objectives and management (Withanage, 2013, slide 28)
|
Project Charter April 4, 2013 |
|||||||||||||||||||
|
Project Tile: Centre Website Project |
|||||||||||||||||||
|
Budget Information: The Centre has allocated a funding of $1,000,000 for this project. More than half of these expenses will be for an outsourced team of web development experts who would build the website in collaboration with the staff at the centre. The rest of the expenses would be for training the staff and IT team as required, in order to continue to develop and manage the website themselves.
Project Manager : Raza Ali Khan, 042 911 1802, raplusk8@gmail.com Project Objectives: Develop a website for the research centre that allows them to showcase their research and findings in an easy to use and presentable manner. This will include providing vital information about the current research projects being carried out by the centre, the outcomes of the completed research projects and information about current events and happenings which are open to public participation. Provide the users of the website with an easy and interactive layout with simple, easy to use navigation throughout the website. Provide researchers with easy to use templates and tools, allowing them to present their research in an effective manner. This website will also feature an archive of all research articles and a “Researcher’s forum”, where the users can discuss and/or collaborate on the projects and ideas that they are working on and also get advice from people involved in the same area. Most parts of this website will be free to users, except for more advanced features such as research data download, which would only be allowed to the relevant stakeholders in the respective research project. This website will also feature options to subscribe to a weekly/fortnightly newsletter to be released by the research centre, which would then be sent via email to the subscribers. Both, the ‘Researcher’s forum’ as well as the weekly/fortnightly newsletter are only accessible to users who have subscribed to the website. Users will have the option to subscribe via email or by using the provided social media plug-ins (Facebook, Twitter and Google plus) to link to their personal social media networks, also making it easier for these users to share the information. |
|||||||||||||||||||
|
Approach: · Communicate with the Bruce and his staff in order to understand their expectations of the website and the type of templates they require, by carrying out a survey to understand their requirements. · Build various sample templates and get feedback from staff, to come up with suitable fits as per staff requirements and current trends. · Research the most suitable software, in order to maintain website security and provide a suitable platform for the “Researcher’s forum” and article retrieval service. · Design a suitable and attractive layout for the website. · Open the beta version of the website for a trial by the staff and get their feedback, making iterative changes as required. · Provide a short training to the staff on the format of the templates and site layout if required. · Train the IT department of the university on managing the website and handing over site maintenance to them. |
|||||||||||||||||||
|
Roles and Responsibilities: Name and Signature |
Role |
Position |
Project Champion |
bruce@gmail.com |
Vice Chancellor |
Project Manager |
raplusk8@gmail.com |
Consultant |
erickolarov@gmail.com |
Steering Committee member |
michael@gmail.com |
|
Comments: (Handwritten or comments from above stake holders, if applicable) |
|
We need to make sure this project is completed with absolute quality, as this will be the face of the project – Alex We need to be careful that the subscribe feature of the website does not drive people away thinking of spam- Raza |
Project Work Breakdown Structure(WBS)
1. Initiating
1.1 Assign a Project Manager
1.2 Prepare Business case
1.3 Stake holder analysis
1.4 Prepare Project Charter
1.5 Kickoff meeting
2. Planning
2.1 Prepare Scope statement
2.2 Prepare team contract
2.2.1 Identify a competitive website development team and contract them
2.3 Prepare Work Breakdown Structure
2.4
Prepare Schedule and cost baseline
2.4.1 Determine task resources
2.4.2 Determine task timelines
2.4.3 Determine dependencies
2.4.4 Draft a Gantt Chart
2.4.5 Discuss and finalize Gantt Chart with key stakeholders
2.5
Prepare work Management schedule
2.6 Identify, discuss and prioritize risks
3. Executing
3.1 Staff inputs for website and researcher’s forum
3.2 Resource procurement
3.2.1 Hardware resources
3.2.2 Software resources
3.3 Database design and construction
3.3.1 Setting up required servers.
3.3.2 Creating an accessible archive for research articles.
3.4 Website design
3.4.1 Website navigation
3.4.2 Website Layout and homepage design
3.4.3 Develop GUI and icons
3.5 Researcher’s forum design
3.5.1 Creating forum access rules and regulations.
3.6 Develop website content
3.6.1 Article templates
3.6.2 Links
3.6.3 Subscription and login security
3.6.4 Configure social media plug ins
3.7 Website Construction
3.8 Website testing
3.8.1 Beta website rollout to users to gather feedback
3.8.2 Making iterative changes as per feedback
3.9 Project Benefits measurement
3.10 Final website rollout for external users
4. Monitoring and controlling
4.1 Status reports and bug fixes
4.1.1 Weekly reports
4.2 Milestone report
5. Closing
5.1 Training staff as required
5.2 Prepare final project report
5.3 Prepare final presentation
5.3 Lessons learned
Stakeholder Register
|
Name |
Internal / External |
Contact Information
Email/ Phone |
||||
|
Bruce Willis |
Research project manager |
Internal | ||||
|
Alex |
Project Sponsor |
alex@gmail.com |
||||
|
Raza Ali Khan |
||||||
|
Eric Kolarov |
International expert on social media research |
External | ||||
|
Michael Cera |
Team lead- Website development |
|||||
|
Hina Khan |
Head of IT |
Steering committee member |
hinakhan@gmail.com |
Stakeholder Analysis/Management Strategy
February 4, 2013
Project name: Centre Website Project
KEY STAKEHOLDERS
|
Name: |
Bruce |
Alex |
||||
|
Organization: |
Head of IT support |
|||||
|
Role in project: |
Project sponsor | |||||
|
Unique facts: |
Skilled MBA with great business acumen, an expert at juggling multiple projects. |
Highly experienced professional, with a strict regard for timelines and quality of work. |
Successfully handled a few IT projects, showing potential as a leader, although relatively less experienced. |
A well known name in the social media space, with a PhD in psychology and a social media research. |
Excellent technical skills and a real professional at delivering quality work under strict timelines. |
Good technical skills and has a good say in all IT projects. Weary of external contractors and the quality of work they deliver. |
|
Level of interest: |
Very high |
Low |
Medium |
|||
|
Level of Influence: |
Very high: Can call the shots. |
Very high: Calls the shots. |
High: Subject Matter expert |
Medium: An expert on social media research |
Medium: Single point of contact to convey feedback and ensure it is acted on. |
High: Gets her points across very well at meetings. |
|
Suggestions on Managing relationship: |
Ensure he reviews work and ask questions wherever required. |
Keep informed of the progress and important milestones. |
Have him constantly review work and get his signoff before managerial review. |
Try to get him interested in the project more as his feedback would be crucial. |
Ensure that he talks to Hina so that she and her team can be on the same page regarding the project and provide their input as well |
Get her involved in all parts of the project, so that she understands all crucial aspects so that the project handover becomes easier. |
Milestone Report for the initiating and planning processes
|
Milestones |
Date |
Status |
Responsible |
Issues / Comments |
||||||||
|
Initiating |
||||||||||||
|
Project Manager assigned |
April 4, ‘13 |
Completed |
Bruce | |||||||||
|
Business case created |
April 14, ‘13 |
Raza | ||||||||||
|
Project Charter signed |
April 25, ‘13 |
|||||||||||
|
Project Kickoff meeting held |
May 2, ‘13 |
|||||||||||
|
Planning |
||||||||||||
|
Scope statement completed |
May 5, ‘13 |
|||||||||||
|
Team contract signed |
May 18, ‘13 |
Went well |
||||||||||
|
WBS completed |
May 26, ‘13 |
|||||||||||
| Prepare Schedule and cost baseline |
June 1, ‘13 |
|||||||||||
| Prepare work Management schedule |
June 23, ‘13 |
Discussed and reviewed with relevant stakeholders. |
||||||||||
|
Identification, discussion and prioritization of risks complete |
June 27, ‘13 |
Raza |
References
1. Heiyanthuduwage, R (2013). Information Technology Project Management [ITC 493 Subject Outline]. Retrieved from Charles Sturt University website: http://interact.csu.edu.au/portal/site/ITC493_201330_S_I/page/241fa317-c408-41e5-00f6-7fb1fbd77dba
2. Withanage,C.P. (2013). Chapter 3(1): Project Management process groups: A case study
[PowerPoint slides]. Retrieved from Charles Sturt University Interact website for ITC 493 website:
http://interact.csu.edu.au/portal/site/ITC493_201330_S_I/page/212ad177-d846-4ffa-804a-5d0f710291b9
�Total Marks=70/80
�Marks=9
�Marks=18/20
�Marks=9
�Marks=10
�Marks=10
�Marks=7
�Marks=7
Sheet1
| $ per Hour | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Project Manager | 8 | 60 | 38 | 40 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Systems Analysis | 20 | 9600 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Web Graphic Designer | 50 | 30 | 12000 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Web Application Programmer | 20000 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Web System Expert | 70 | 22400 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Program Team member_1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Program | Team Member_2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quality Assurance Tester | 14400 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Database Administrator | 16000 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Team Member_1 | 35 | 14000 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Total Duration for the Project | 3 months | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Working Days | 5 days per week ( No Over time required) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Working Hours | 8 hours per day ( 8.30 – 5.30pm) – 1 hour for lunch | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Project Start Date | 3rd of June 2013 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Total Budget | 150,000 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Please note that only the Project Manager and the team members can work full time during the whole project duration. |
Sheet2
Sheet3
Project Management
Report – 2
Assignment 2
Project Management Report – 2
Research center website
Assignment 2
Submitted By:
Agha
Hasan Mirza (ID: 11509306)
Lecture: Dr. Chandana Withana
ITC493 – IT Project Management – Assignment 2
Content:
Page No.
Introduction ……………………………………………………………..…………………..…………. 03
WBS
of research center website …..………………………..………….………….………… 03
Gantt Chart
………………………………………….………..…….…………………………………… 06
· Critical path diagram ………………………………….……………………………….. 07
· Network diagram ………………………………………..………..…………………….. 08
Budget ………….………..………………………………………………………………………………… 09
Risk
registration ……………………………………….……………………..………………..…..… 10
· Project risk chart ………………………………………..………..…………………….. 10
· Risk responsibilities & roles …………………………………..…………………….. 11
· Types of risk …………………………………………….…………..…………………….. 11
·
Quality
planning …………………………………………..………..…….…………….. 12
RACI chart …….………..……………………………………………………………………..……….. 12
Stakeholder
communications plan ……….…………………………..…………………….. 15
· Stakeholder Agreement chart …………….……………………..……………….. 16
References ……………………………………………………………………..…………..………….. 17
Introduction
The Research Center website time period for this project start Jan 2013 and finish June 2013 estimate times are 6 months. In research website team (Ence Pvt. Ltd.) some of guys more than 10 years serving the world web application technologies. this website database easy to assess not only research center even world-wide if someone interested about technology research this website for them as well this website customer not only students even professor, lecture, doctors, scientist & many more those have interest in this field. Our company designing database for this sort of in future any type of application even language can assess these data it has been store in xml files.
Ence Pvt. Ltd. (Research center website team) plan to implement a new system that is risks issues on it. Properly chances to system failed but good market research minimum the risk after finish this project 6 month supports & some upgrades time to time.
· This project time management needs an in Gantt chart and critical path diagram which defined to completion research center project.
· This Project cost involves in overall budget this makes sure research center team members done this project within limited budget.
· Risk registers to makes sure the project risk classification throughout of the project and that is solving the risk.
· People management involves make sure efficient use for user & shareholders.
·
Closing
the project, the most significant part of this research center project.
WBS of Research Center Website
All reseach center web application of course uniquse, so type of uniquse modules involved various expert of particular module. For purposes of social media website just think in terms of general purpose. gather information user or student visit site. But due to technical reason administrator don’t have that much data to upgrade system so user never return on this site but if same information user or someone else have then they are capabale to update that information like social networking into research center website. So that mean maybe more requiredment & you have to expand your WBS suitably.
What the main key pieces of this project work. You might be itemization actions or deliverables reliant on your project. This is a example you may start out with list of as such as the starting point for a WBS for the research center website.
WBS for Research Center website
WBS phase one deploying a website structure. What should research center website need for sharing research plus private to share particular people Facebook is good example for social media website. There is some permission for each type of users. In my web tree structure to views this WBS. I provide those things as well that you can see following content.
1.0
Initiating
1.1
Evaluation & Recommendations
1.2
Project Charter
1.3
Business Case
1.4
Stakeholder Analysis
2.0
Planning
2.1
Kick-off Meeting
2.2
Scope
Statement
2.3
Quality / Risk Management Plan
2.4
WBS
2.5
Gantt Chart
2.6
Resource Allocation
3.0
Executing
3.1
Develop Schedule for Project
3.1.1
System Requirement Development
3.1.2
Conceptual Design Development
3.1.2.1
Data and Process Conceptual Design
3.1.3
Architectural Design Development
3.2
Website Design Development
3.2.1
Methods and Evaluation for Web Design
3.2.2
Graphical Treatment for GUI
3.2.3
Data Designing
3.2.4
Information Architecture
3.2.5
Design Aspect of Style Guide
3.2.6
Technical Aspect of Design Guide
3.3
System Requirement Components
3.3.1
Database System Modules
3.3.2
System Coding Components
3.3.3
GUI Interface Modules
3.4
Database Integration
3.
4.1
Database Testing
3.
4.2
Site Map Creation
3.
4.3
Approve Tests
4.0
Monitoring and controlling
4.1 Project Management
4.2
Project Status Meetings
4.3
Risk management
4.4
Update Project Management Plan
5.0
Closing
5.1
Official Close
5.1.1
Final Presentation
5.2
Lesson Learnt
5.3
Staff Training
5.4
User Menu
Gantt chart
It’s a Gantt chart generated though MS Project 2010 according to WBS.
Critical Path Diagram
Here is critical path diagram generated though MS project 2010. According to MS project critical path will 976 hours
Network Diagram
It’s a network diagram that goes to end of death line of this project that is 6 months so critical path though should be in 976 hours
Budget
Team structure for research center projects
Estimated time & cost of resources
Budget Report
Total budget cost = $233,395.00
Risk registration chart
Analyzing & counter the risk throughout the project life circle it will increase the productive of project.
Project risk chart
|
Customary Area |
Risk Situation |
|
Beginning |
The lean supply; poor review of project |
| Scope |
unfinished scope; concept not clear |
|
Time |
Resources not defined properly project over deadline and resource are not anticipated correctly; poor management of project. |
|
Cost |
Poor scheduling; not sufficient productivity. |
| Quality |
Assurance of poor quality of project |
|
Human Resource |
Not proper leadership; less productively |
|
Communication |
Not proper communication stakeholders; |
| Risk |
Poor plan; security issues |
|
Procurement |
Unenforceable condition |
Risk responsibilities & roles
When companies launch a new website; they notoriously rush to strengthen sales efforts not surprisingly, nine out of ten website product launches fail because of a flawed business model. Business Weak value proposition
The purpose of quality planning is provided essential website for users. Testing & analysis system provided good quality & prevent bugs in projects.
Risk Responsibilities & maintain quality
|
Role |
Main responsibilities |
|
|
Project Manager |
Maintain the completion of quality |
|
|
Team Member |
Assign project quality each project |
|
|
Quality Management |
· Manage the quality product · Review of project manager |
|
|
Project Executive |
· Final confirmation of the project conferrable · Monitor modules risks · Any change any leave info program coordinator |
There are several type risk categories.
Market risk
· Investing IT project chance to change technology & old technology not reminds useful enough
· Poorly defined target market
Planning Risk
· Disorganized distribution scheme
· Proper planning save time & resources & project finish before time period
(+ positive risk)
Financial risk
· Financial market collapse currency rate going up.
· Economy doing well & market Australian dollar going up (+ positive risk)
Technology risk
· Technology change & all project upgrade according to new technologies
People risk
· Staff change to rapidly
· Divide in many modules more faster completions (+ positive risk)
Structure risk
· Because of earth quick building structure get some issue due to this reason effect a project.
· High cost structure
Quality Planning
While the introduction above explains the key reasons for failure in simple terms, implementing real-world solutions in the current business environment is not so simple. There are many dynamics affecting the enterprise sales process in today’s business landscape. Consider the following examples.
The client communication process that must run in parallel with web development an enterprise web developers understanding of customer problems and needs – a process which is calls “Customer Development” – is driven by four factors:
· Customer Discovery – drives understanding of customer problems and needs
· Customer Validation – develops a sales model that can be replicated
· Customer Creation – creates and drives end-user demand
· Company Building – transforms an organization from mere earning to one designed for execution
RACI Chart
The RACT model is used define roles, responsibilities during organization the project process.
In this RACI chart I define responsibilities roles head of department. What the process to follow this structure. You will see in this chart
|
Project Modules |
Stakeholder |
Project Leader |
Team Leader |
|||||||||||||||||||||||||||||||||||||||||||
| 1.0 |
Initiating |
C, A |
R |
|||||||||||||||||||||||||||||||||||||||||||
| 1.1 | Evaluation & Recommendations |
I |
A, R |
C |
||||||||||||||||||||||||||||||||||||||||||
| 1.2 | Project Charter |
R, A |
||||||||||||||||||||||||||||||||||||||||||||
| 1.3 | Business Case |
I, C, A |
||||||||||||||||||||||||||||||||||||||||||||
| 1.4 | Stakeholder Analysis |
A, C |
||||||||||||||||||||||||||||||||||||||||||||
| 2.0 | Planning | |||||||||||||||||||||||||||||||||||||||||||||
| 2.1 | Kick-off Meeting |
A |
||||||||||||||||||||||||||||||||||||||||||||
| 2.2 |
Scope Statement |
|||||||||||||||||||||||||||||||||||||||||||||
| 2.3 | Quality / Risk Management Plan | |||||||||||||||||||||||||||||||||||||||||||||
| 2.4 | WBS | |||||||||||||||||||||||||||||||||||||||||||||
| 2.5 | Gantt Chart | |||||||||||||||||||||||||||||||||||||||||||||
| 2.6 | Resource Allocation | |||||||||||||||||||||||||||||||||||||||||||||
| 3.0 | Executing | |||||||||||||||||||||||||||||||||||||||||||||
| 3.1 | Develop Schedule for Project | |||||||||||||||||||||||||||||||||||||||||||||
| 3.1.1 | System Requirement Development |
R, A |
||||||||||||||||||||||||||||||||||||||||||||
| 3.1.2 | Conceptual Design Development | |||||||||||||||||||||||||||||||||||||||||||||
| 3.1.2.1 | Data and Process Conceptual Design | |||||||||||||||||||||||||||||||||||||||||||||
| 3.1.3 | Architectural Design Development | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2 | Website Design Development | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.1 | Methods and Evaluation for Web Design | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.2 | Graphical Treatment for GUI | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.3 | Data Designing | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.4 | Information Architecture | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.5 | Design Aspect of Style Guide | |||||||||||||||||||||||||||||||||||||||||||||
| 3.2.6 | Technical Aspect of Design Guide | |||||||||||||||||||||||||||||||||||||||||||||
| 3.3 | System Requirement Components | |||||||||||||||||||||||||||||||||||||||||||||
| 3.3.1 | Database System Modules | |||||||||||||||||||||||||||||||||||||||||||||
| 3.3.2 | System Coding Components | |||||||||||||||||||||||||||||||||||||||||||||
| 3.3.3 | GUI Interface Modules | |||||||||||||||||||||||||||||||||||||||||||||
| 3.4 | Database Integration | |||||||||||||||||||||||||||||||||||||||||||||
| 3.4.1 | Database Testing | |||||||||||||||||||||||||||||||||||||||||||||
| 3.4.2 | Site Map Creation | |||||||||||||||||||||||||||||||||||||||||||||
| 3.4.3 | Approve Tests | |||||||||||||||||||||||||||||||||||||||||||||
| 4.0 | Monitoring and controlling | |||||||||||||||||||||||||||||||||||||||||||||
| 4.1 | Project Management | |||||||||||||||||||||||||||||||||||||||||||||
| 4.2 | Project Status Meetings | |||||||||||||||||||||||||||||||||||||||||||||
| 4.3 | Risk management | |||||||||||||||||||||||||||||||||||||||||||||
| 4.4 | Update Project Management Plan | |||||||||||||||||||||||||||||||||||||||||||||
| 5.0 | Closing | |||||||||||||||||||||||||||||||||||||||||||||
| 5.1 | Official Close | |||||||||||||||||||||||||||||||||||||||||||||
| 5.1.1 | Final Presentation | |||||||||||||||||||||||||||||||||||||||||||||
| 5.2 | Lesson Learnt |
C, R |
||||||||||||||||||||||||||||||||||||||||||||
| 5.3 | Staff Training | |||||||||||||||||||||||||||||||||||||||||||||
| 5.4 | User Menu |
R = responsibility, A = accountability, only one A per task, C = consultation, I = informed
Stakeholder Communications Plan
When it come communication plan the wise choice of organization for project manager to communicated with shareholders. This is categorizes deliverable of communication getaway & both side receiving & distribute information from organization stakeholder.
Proposal
The proposal of communication is time & consistency
Communication channel
·
Face to face
· Telephone
· Emails
Communication Matrix
|
Communication type |
Objective of communication |
Medium |
Frequency |
Audience |
Owner |
||
|
Kickoff meetings |
Introduction about project and team. Review project goals and compress |
Face to Face |
Once |
-Project Sponsor – Project Team Stakeholders |
Project manager |
||
|
Project team Meetings |
Review the status of project with team |
-Face to Face -Conference call |
Weekly |
Project Team | Project manager | ||
|
Technical Design meetings |
Discuss the issues those one faced on design, technical and development |
Face to face |
As needed |
Project Technical Staff |
Technical lead |
||
|
Monthly project status meetings |
Report about the project to the project manager |
-Face to Face
– Conference call |
Monthly |
Project Manager |
|||
|
Project status Report |
Report about the status of the project Including: issues, progress activities and costs. |
|
Monthly |
· Project Sponsor · Project Team · Stakeholders |
Project charter agreement
Documentation Date: 26, August 2012
Project title: Website Development for Research Center
Project Start Date: 1, January 2013
Finishing Date: 30, June 2013
Budget Information: The estimated budget cost $203,395.00 to consider risk factor add more 13% budget on it so cost $233,395.00 includes all team leader, programmer, tester, trainer programmer, administrator (all resources) plus user tester mode plus if something hard is malfunctioning include in budget.
Project Manager Details: Agha H. M. +61 4312 888 76,
agha@hotmail.com.au
Project Objectives: develop a website for research point of view everyone can share own point & share a research theory, professor share own research on website so for master & doctorate labels student can choose research & help particular research & those student also can share own research for everyone if they wanted & everyone can comments them for track all research & comments there are administrator there to control all things if something is harmful so it’ll have power to take a action against that person. This will available for everyone. Not only research center outside of research center (that research want to share with public).
Approach: This website project divide eight section & last section testing section it’ll launch a demo website that everyone can used it & share idea & comment, error & more. Controlling all research material administrators has more power than any other.
· Training mode also for programmer based & user based in starting
· Measure duties to care of server Software, upgrades & technologies
· Encourage to other help to share research & help on it
Roles & Responsibilities
|
Name |
Contact Details |
Signature |
|
Alex |
Direction |
alex@gmail.com |
| Agha |
agha@hotmail.com.au |
|
|
Naveen |
naveen_vharm@ence.net.au |
|
|
Ravi |
ravi@usa.net |
Comments
· Project cost is various according to recover to research center
· Website not reasonable if any researcher public his/her research & that want to private
· I want some review of research center team. So I can add more function or change my functionality
References
· Channel ship, (August/2012), Social media SWOT analysis,
http://www.channelship.ie/blog/post-570-social-media-swot-analysis-whats-your-opinion.php
Aniko communication, (August/2012), Social media SWOT analysis,
· Information Technology Project Management. (August/2012). JWD Consulting Intranet Site Project Baseline Gantt Chart
· Information Technology Project Management, Project chart. (August/2012). The purpose of the project charter is to document
· Schwalbe, K. (2010). Informaation technology project management (6th Ed.). United States of America: Course Technology
· Hartley,S.(2003) Project management: a competency –based approach, Person Hall, Australlia
· Larson, E. Gray , C.(2011) Project Management the Managerial Process (5th ed.). Singapore: McGRAW.HILL
7
