Week 3 Project Progress

Company Organization Chart

Company Profile

In this week 3 meeting, we have disscussing about the organization chart for our own company and also the task distribution according to the position of the person.

In this week also,we have identified and make some analysis about the knowledge on Software Project Management.Below are the example of the knowledge based that we has been identified:

Knowledge Category 1:Principles of Software Project (Mandatory) Domain Description: Vocabulary, concepts and principles of Software Project Management. Broad overview of the other domains. Major emphasis on the role of the Project Manager from start of a software development project to the conclusion. Documentation samples might include one of the following: List of activities done by the candidate from beginning to end of a typical project in his/her organization A Project Plan

Knowledge Category 2 :Risk Management Domain Description: Principles of risk Risk analysis Understanding of the risks that are unique or emphasized in software projects How to quantify risks Tradeoffs associated with emphasizing one software characteristic versus another Internal Control & Security. Documentation samples might include one of the following: Sample of a completed risk assessment used by the candidate on a project and the risk management plan that accompanies it. Security Plan.

Knowledge Category 3 :People Management (includes Communications) Domain Description: An understanding of how to man a software development project. How to train individuals in the skills needed for software development. All human resource issues associated with managing a project. Customer Liaison. Communication. Teams, Groups, Leadership, Role of Senior Management. Negotiation. Processes used to interact with customers/users throughout the software development lifecycle - knowledge of how to assess customer attitudes about development, including concepts such as customer surveys, focus groups, assessment questionnaires, and how to assist customers in the acceptance testing aspects of software development. Emphasis is on service level agreements or equivalent. Procurement Management. Internal Control & Security. Documentation samples might include one of the following: Sample of a resource/staffing chart prepared by the candidate that was used to assign personnel to a project. Sample of plans to train the assigned team. Sample plans of communication with the customer. Sample plans of internal communication. Plan to resolve customer requests. May include actual customer surveys, assessment reports, and questionnaires. Security Plan.

Knowledge Category 4 :Schedule and Budget Management Domain Description: Principles on how to create a software project budget and schedule using either manual processes or automated packages. Associated Techniques such as critical path, resource lending and re-calibration when changes are made to the project plan resources, budget, schedule and/or risk. Work Breakdown Structure (WBS) Estimation – FPA and other methods Cost & Budget Management. Documentation Example: Sample of an MS Project Plan, or other S/W PM tool output or manual GANT charts, prepared by the candidate which includes how resources were allocated to a project. How budget and/or schedule changes were compensated in the on-going plan.

Knowledge Category 5 :Project Control Domain Description: Relationship of control to risk. Types of control that can be incorporated into project management (i.e., preventative, detective, and corrective). Understanding of the principles of quality control. How quality control is used throughout the project to assure the processes are utilized correctly, the entrance and exit criteria are correct, and that problems are identified early in the process. Status reporting. Scope management. Change control plan Documentation samples might include one of the following: Software Quality Plan detailing a project's critical success factors and how the Project Manager intended to ensure the project quality. This is not the same as a RM plan, but the two may be combined into one document. Document addressing changes

Knowledge Category 6 :Business Requirements Domain Description: How requirements are defined, Attributes of a good requirement. Processes that can be used to define good requirements like - Joint Application Development (JAD). Change management. How to trace requirements throughout the software development effort using techniques such as Quality Function Deployment (QFD) Documentation samples might include one of the following: A representative sample (no more than 10 pages) of a requirements document actually used on a project that was managed by the candidate and the accompanying test plans (no more than 5 pages each) demonstrating traceability from requirements to end product. Clearly define which techniques were used (JAD,QFD, Other).

Knowledge Category 7:Status Reporting and Measurement Domain Description: Principles of measurement and how they apply to managing a software development project. How to develop reports that indicate the status of development of a software project (e.g., what percent of the project has been completed versus what percent of the time has been expended). Familiarity with measurement concepts such as key indicators and project management dashboards. What was measured in the project. Managing the status of the project time. Documentation samples might include one of the following: Sample status report and/or measurement report that indicates what measures were being tracked and the degree to which the project met/is meeting its measurement objectives. These measures could be related to the critical success factors, budget schedule and / or resources. May be accompanied by samples of a project management dashboard if one was developed for the project.

Knowledge Category 8 :Software Development Processes Domain Description: Understanding of how processes are developed and improved, including the components of a process which are policy, standards, procedures (i.e., do and check procedures), and guidelines. Understanding of the importance of entrance and exit criteria at each stage of software development. Types of software development processes (e.g., waterfall and spiral development processes). Understanding of the major phases of software development. Types of deliverables produced during each phase, and the objective of each deliverable. Prototyping. Documentation samples might include one of the following: A document detailing the type of SDLC undertaken, how the project will be developed, tested, and delivered. Any alternative development methods that were proposed by the Project Manager. May also include process flows, ER Diagrams, cases or context diagrams developed for the project. MINUTES OF MEETING ON WEEK 3 Company : Pavilion Wonderland Sdn.Bhd Date : 18 January 2009 Time : 9.00 pm – 10.00 pm Venue : in front of BPA Office Attendees : 1. Phang Shiuh Yaw General Manager 2. Wan Nazirah Wan Mohamad Secretary 3. Noor Erfia Farina Binti Dajali Academic Manager 4. Zairie Bin Mat Zain Academic Manager 5. Mohd Hafiz Bin Mohd Nor IT Manager 6. Mohd Islahuddin bin Mohd Shahrir IT Manager 7. Wan Muhammad Izran bin Wan Muhammad Said Human Resource Manager 8. Anis Amilah Binti Shari Human Resource Manager Agenda: Organization chart Knowledge in SPM 1. Organization Chart In this week 3 meeting, we have discussing about the organization chart for our own company and also the task distribution according to the position of the person. The company organizational chart and company profile can be seen as below Company Organizational Chart Company Profile 2. Knowledge in SPM In this week also, we have identified and make some analysis about the knowledge on Software Project Management. Below are the example of the knowledge based that we has been identified and for the detailed each knowledge can be refer to our official blog. Knowledge Category 1:Principles of Software Project (Mandatory) Knowledge Category 2 :Risk Management Knowledge Category 3 :People Management (includes Communications) Knowledge Category 4 :Schedule and Budget Management Knowledge Category 5 :Project Control Knowledge Category 6 :Business Requirements Knowledge Category 7:Status Reporting and Measurement Knowledge Category 8 :Software Development Processes . All the above task given which have been finish, will be bring forward to the next meeting on week 4 for checking. Meeting was adjourned at 10.00 pm. Next meeting is scheduled a week from now, i.e. 25 January 2009, same venue and time. All members’ actions are to present their feedback. Minutes prepared by: Check by: ………………………… ……………………………… ( Wan Nazirah Wan Mohamad) (Phang Shiuh Yaw) Secretary General Manager

Posted by Pavilion Sdn. Bhd.

Week 2 Project Progress

Hi all,
In this week,our group have a discussion for the second time.As usual,the meeting was successfully conduct in front of the PPA office with full attendance of group members.

The purpose of this meeting is actually to choose the company who are most suitable to do our project,Introduction to ASP.net(we act as a SO) since we got three(3) proposal which is from Software to Seek Corporation(S2S), 6Centuries Sdn. Bhd, and Nine-tech Company. We have to choose only one Company to develop our project.

After the discussion, the decision has been made.All group members was agreed to choose 6Centuries Sdn.Bhd to develop our project. The main reason why we choose the 6Centuries company is because,compare to the other company, 6Centuries has been awarded Software Quality Assurance 2009 which is, that awarded can guarantee us the project will be fulfil the quality standard. Beside that, 6Centuries Sdn.Bhd has done many project with the other company which means they have a lot of exprience in this field.
To see the other reason why we agreed to choose 6Centuries Sdn.Bhd to develop our project can be see on the table below:



As a SC, among the proposal that we have propose to Software to Seek Corporation(S2S), 6Centuries Sdn. Bhd, and Nine-tech Company, only one proposal has been chooese to develop their project.We were choose to develop a Petakom Official Website project from 6Centuries Sdb.Bhd. This is because the specification that they want meets all the knowledge,skill and so on that we have. They also very interseted with our proposal and it make them agreed to choose our proposal.We hope that we can impressed 6Centuries Sdn.Bhd with our skills and gladly to choose us fo the next project.

Pavilion Sdn.Bhd & 6Centuries Sdn.Bhd

Picture above shows that our Leader,Ah Yaw shake hands with Azmi from 6Centuries company during the contract signing.

MINUTES OF MEETING ON WEEK 2

Company : Pavilion Wonderland Sdn.Bhd Date : 11 January 2009 Time : 9.00 pm – 10.00 pm Venue : in front of BPA Office Attendees : 1. Phang Shiuh Yaw General Manager 2. Wan Nazirah Wan Mohamad Secretary 3. Noor Erfia Farina Binti Dajali Academic Manager 4. Zairie Bin Mat Zain Academic Manager 5. Mohd Hafiz Bin Mohd Nor IT Manager 6. Mohd Islahuddin bin Mohd Shahrir IT Manager 7. Wan Muhammad Izran bin Wan Muhammad Said Human Resource Manager 8. Anis Amilah Binti Shari Human Resource Manager Agenda: Choose the company Others topic 1. Choose the Company The purpose of this meeting is actually to choose the company who are most suitable to do our project, Introduction to ASP.net (we act as a SO) since we got three (3) proposals which is from Software to Seek Corporation (S2S), 6Centuries Sdn. Bhd, and Nine-tech Company. We have to choose only one Company to develop our project. All group members was agreed to choose 6Centuries Sdn.Bhd to develop our project. The main reason why we choose the 6Centuries company is because, compare to the other company, 6Centuries has been awarded Software Quality Assurance 2009 which is, that awarded can guarantee us the project will be fulfill the quality standard. Besides that, 6Centuries Sdn.Bhd has done many project with the other company which means they have a lot of experience in this field. To see the other reason why we agreed to choose 6Centuries Sdn.Bhd to develop our project can be seen on our official blog. 2. Others topic The others issues that has been discuss was: Any difficulties during doing the task Any moral excellence, virtuousness of the members are discussed . All the above task given which have been finish, will be bring forward to the next meeting on week 3 for checking. Meeting was adjourned at 10.00 pm. Next meeting is scheduled a week from now, i.e. 18 January 2009, same venue and time. All members’ actions are to present their feedback. Minutes prepared by: Check by: ………………………… ……………………………… ( Wan Nazirah Wan Mohamad) (Phang Shiuh Yaw) Secretary General Manager

Lastly, thank you all the attendance and information sharing of member. Kindly to leave a comments.

Posted By Pavilion Sdn. Bhd.

Week 1 Project Progress

The first week of the class started, Project Software Management grouped us together to have a ice breaking session on 9pm, 4th January 2009 at in front of PPA office. Full Attendance of member.

Member:
Anis Amilah binti Shari
Mohd Hafiz bin mohd Nor
Mohd Isslahuddin b Mohd Shahrir
Noor Erfia Farina binti Dajali
Phang Shiuh Yaw
Wan Nazirah bt Wan Mohamad
Zairie bin Mat Zain

The ice-breaking session started with project introduction, member introduction, contact between member. Task distribution wan the core task in this meeting, as lecturer request us to produce a RFP or RFQ. First of all, we are totally confuse between SO and SC, but we identify the characteristic of SO and SC, we get the brief idea wat we going to do next. We was proposed our project title from members respectively. We considered on the development time, documentstion, progress, update, etc. Between , we discussed on the way of presentaion as a SO, we dicided Mr. Phang Shiuh Yaw as our first presenter from our company. The slide is produced by all the member in the discussion. Moreover, we dicided on our company name, Pavilion Sdn Bhd, which gain from the PC name and the meaning of pavilion. We take around 30 minute for the preparation of information to be present in the binding conference. Beside, we dicided to obtain 3 proposals from all the SO which allowed us to make discussion and consideration on project chose as we are SC too.

The meeting was ended around 10.00. The outcome in the meeting was:

• setup a company,
• name the company,
• distributed task according to guildeline,
• produce our presentation slide,
• share opinion on project selection, and present,
• setup a standard format of proposal
• setup web page or blogs which all member allowed to access
• discuss on project specification, profile, background, organization, targeted company, cost,
• next meeting agenda , time , place, purpose

Minutes Meeting On Week 1

Company : Pavilion Wonderland Sdn.Bhd Date : 4 January 2009 Time : 9.00 pm – 10.00 pm Venue : in front of BPA Office Attendees : 1. Phang Shiuh Yaw General Manager 2. Wan Nazirah Wan Mohamad Secretary 3. Noor Erfia Farina Binti Dajali Academic Manager 4. Zairie Bin Mat Zain Academic Manager 5. Mohd Hafiz Bin Mohd Nor IT Manager 6. Mohd Islahuddin bin Mohd Shahrir IT Manager 7. Wan Muhammad Izran bin Wan Muhammad Said Human Resource Manager 8. Anis Amilah Binti Shari Human Resource Manager Agenda: Organization Briefing Task briefing Create Blog for company 1. Organizational Briefing For the first time meeting, the group has discussed about the company name, our organizational and whatever topic that related with the company. After the discussion, we have agreed to give a name for our organizational, Pavilion Wonderland Sdn.Bhd. The person and his/her position as below: 1. Phang Shiuh Yaw General Manager 2. Wan Nazirah Wan Mohamad Secretary 3. Noor Erfia Farina Binti Dajali Academic Manager 4. Zairie Bin Mat Zain Academic Manager 5. Mohd Hafiz Bin Mohd Nor IT Manager 6. Mohd Islahuddin bin Mohd Shahrir IT Manager 7. Wan Muhammad Izran bin Wan Muhammad Said Human Resource Manager 8. Anis Amilah Binti Shari Human Resource Manager 2. Task briefing First of all, we are totally confuse between SO and SC, but we identify the characteristic of SO and SC, we get the brief idea what we going to do next. We was proposed our project title from members respectively. We considered on the development time, documentation, progress, update, etc. Between, we discussed on the way of presentation as a SO, we decided Mr. Phang Shiuh Yaw as our first presenter from our company. The slide is produced by the entire member in the discussion. Moreover, we decided on our company name, Pavilion Sdn Bhd, which gain from the PC name and the meaning of pavilion. We take around 30 minute for the preparation of information to be present in the binding conference. Besides, we decided to obtain 3 proposals from all the SO which allowed us to make discussion and consideration on project chose as we are SC too 3. Create Blog for Company For this task, the company has been given the task to Mr Phang Shiuh Yaw and Mr. Zairie. Both of them will have the responsibility about the blog progress. All the progress report and project progress will be uploading on the blog. The address of the blog is http://paviliongroup1.blogspot.com . All the above task given which have been finish, will be bring forward to the next meeting on week 2 for checking. Meeting was adjourned at 10.00 pm. Next meeting is scheduled a week from now, i.e. 11 January 2009, same venue and time. All members’ actions are to present their feedback. Minutes prepared by: Check by: ………………………… ……………………………… ( Wan Nazirah Wan Mohamad) (Phang Shiuh Yaw) Secretary General Manager

Lastly, thank you all the attendance and information sharing of member. Kindly to leave a comments.


Posted by Pavilion Sdn. Bhd.