Your SlideShare is downloading. ×
Project Description:Custom Closet is a webapplication which allowscustomers to beinvolved in the designprocess and ordercu...
Document ControlContributorsName/Position                        OrganizationCara Murphy                          DIT, Aun...
Table of Contents1.INTRODUCTION..............................................................................................
Introduction1.1 Purpose of the DocumentThis document presents the group charter for the team Custom Closet.1.2 AudienceThi...
3. Project Management and Agile Methods:   http://en.wikipedia.org/wiki/PM_Declaration_of_Interdependence ,   http://alist...
CharterID    Item1.0   To call a meeting      Meetings can be called at 24 hour notice.2.0   Meeting notification      Mee...
3.0     Decisions        Decisions require a majority decision: 4 votes.        Each team member has 1 vote.4.0     Votes ...
7.0   Minutes      At each meeting minutes MUST be kept based on the agreed template.      At the beginning of the meeting...
8.0     Distribution of the Minutes        The minutes of each meeting will be distributed by e-mail using the following f...
Team Organisation1.6 Project PhasesThe roles of team members are assigned at team meetings based on the project lifecycle ...
1.7 RolesThis table is a work in progress, as roles are assigned in project meetings the table will be updated.1.7.1   Pha...
Communication Plan1.8 Project TeamCommunication between team members will be via e-mail, skype – chat  voice and meetings....
Project tools and environment1.9 Project ToolsThe following software tools will be used throughout the project:  Tool Name...
1.11 Document naming standardsDocuments are named as follows:     Document Type                                  Naming co...
1.12 Project Filing structureGroupCharter_ProjectCode_v1     Page 15 of 17
Group charter projectcode_v1
Group charter projectcode_v1
Upcoming SlideShare
Loading in...5
×

Group charter projectcode_v1

197

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
197
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Group charter projectcode_v1"

  1. 1. Project Description:Custom Closet is a webapplication which allowscustomers to beinvolved in the designprocess and ordercustom clothing forthemselves through awebsite.Group CharterDate : 7/12/2011 20Authors: Cara MurphyVersion: 1Status: Completed
  2. 2. Document ControlContributorsName/Position OrganizationCara Murphy DIT, Aungier StreetFabrizio Valerio Covone DIT, Aungier StreetChristopher Conlan DIT, Aungier StreetStephen Carberry DIT, Aungier StreetShane Ellis DIT, Aungier StreetVersion HistoryDate Version StatusDecember 7, 2011 1 2
  3. 3. Table of Contents1.INTRODUCTION........................................................................................................................................ 6 1.1PURPOSE OF THE DOCUMENT............................................................................................................................. 6 1.2AUDIENCE...................................................................................................................................................... 6 1.3KEY TERMINOLOGY......................................................................................................................................... 62.PROJECT PROCESS OVERVIEW........................................................................................................... 7 2.1PROCESS CHOICE.............................................................................................................................................7 2.2PROCESS OVERVIEW........................................................................................................................................ 7 2.3PROCESS PRACTICES........................................................................................................................................ 8 2.4REFERENCES................................................................................................................................................... 83.CHARTER.................................................................................................................................................. 104.TEAM ORGANISATION.......................................................................................................................... 11 4.1PROJECT PHASES........................................................................................................................................... 11 4.2ROLES......................................................................................................................................................... 125.COMMUNICATION PLAN...................................................................................................................... 13 5.1PROJECT TEAM ............................................................................................................................................ 136.PROJECT TOOLS AND ENVIRONMENT ............................................................................................ 14 6.1PROJECT TOOLS ........................................................................................................................................... 14 6.2PROJECT PROTOTYPING ENVIRONMENT ............................................................................................................ 14 6.3PROJECT DEVELOPMENT ENVIRONMENT ........................................................................................................... 14 6.4PROJECT MEDIA TOOLS ENVIRONMENT ........................................................................................................... 15 6.5PROPOSED DEVELOPMENT ENVIRONMENT ......................................................................................................... 15 6.6DOCUMENT NAMING STANDARDS...................................................................................................................... 16 6.7 PROJECT FILING STRUCTURE........................................................................................................................... 177.APPENDIX................................................................................................................................................. 188.XXX............................................................................................................................................................. 19GroupCharter_ProjectCode_v1 Page 3 of 17
  4. 4. Introduction1.1 Purpose of the DocumentThis document presents the group charter for the team Custom Closet.1.2 AudienceThis document is aimed primarily both internally at the group and Course Coordinator but will also be usedin the third phase of the Integrated Project as a reference guide.Project Process Overview1.3 Process choiceThe project methodology chosen for this project is Agile.1.4 Process OverviewAgile project management is an iterative method of determining requirements for engineeringdevelopment projects in a highly flexible and interactive manner. Agile techniques are best used in small-scale projects or on elements of a wider programme of work.Agile techniques may also be called extreme project management. It is a variant of iterative life cycle wheredeliverables are submitted in stages. One difference between agile and iterative development is that thedelivery time in agile is in weeks rather than months. Since agile management derives from agile softwaredevelopment, it follows the same standards defined in the agile manifesto when it comes to collaboration anddocumentation. Several software methods derive from agile, including scrum and extreme programming.1.5 References1. Agile Methodologies in general: http://en.wikipedia.org/wiki/Agile_software_development2. Agile Manifesto & Principles: http://agilemanifesto.org/ , http://agilemanifesto.org/principles.html 4
  5. 5. 3. Project Management and Agile Methods: http://en.wikipedia.org/wiki/PM_Declaration_of_Interdependence , http://alistair.cockburn.us/index.php/The_declaration_of_interdependence_for_modern_management4. Cohen, D., Lindvall, M., & Costa, P. (2004). An introduction to agile methods. In Advances in Computers (pp. 1-66). New York: Elsevier Science.5. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile Software Development Methods: Review and Analysis. VTT Publications 4786. Extreme Programming Explained by Kent Beck.GroupCharter_ProjectCode_v1 Page 5 of 17
  6. 6. CharterID Item1.0 To call a meeting Meetings can be called at 24 hour notice.2.0 Meeting notification Meetings may be communicated verbally but there should always be an e-mail/text message notification. An Email notification will have the following format: (1) Subject: [PROJECTNAME]MEETING: DD, DDD, MM, YY (2) Body: Date Time: Location: Called by: Agenda: Actions due: (if any) Decisions pending: (if any) Deliverables due: (if any)2.1 Meeting notification response Meetings notifications MUST be responded to. A meeting notification reply will have the following format: (1) Subject: [PROJECTCODE]MEETING REPLY: DD, DDD, MM, YY (2) Body: Attendee Name: Attending: yes/no If unable to attend Reason for non attendance: Alternative datetimelocation suggestion: 6
  7. 7. 3.0 Decisions Decisions require a majority decision: 4 votes. Each team member has 1 vote.4.0 Votes Votes can be cast verbally at meetings when a vote is called. Votes can be cast by e-mail where an e-mail vote is called.5.0 E-Mail Votes E-mail vote calls follow from an e-mail which specifies the following: (1) Subject: [PROJECTCODE]VOTE: (2) Body: Vote Name: (short name e.g. To UCD or not) Vote Topic: (A question with potential options) Vote due by: (date time must submit by) There should always be discrete options or an answer Yes No. Where new options are proposed then a new vote must be called with the option included and the previous vote cancelled. There should be a vote on the need to call a new vote. Where no vote decision is reached a vote may be called on the list of shortlisted options.6.0 E-Mail Votes Responses E-Mail vote call responses should have the following format. (1)Subject:[ PROJECTCODE]VOTE REPLY: vote name (2)Body: Vote Name: Vote Responder: (your name) Vote decision: (yes, no, or option) Vote comment: (a comment on the reason for your decision) ALL VOTES MUST BE RESPONDED TO AND MUST INCLUDE A COMMENT.GroupCharter_ProjectCode_v1 Page 7 of 17
  8. 8. 7.0 Minutes At each meeting minutes MUST be kept based on the agreed template. At the beginning of the meeting a chairperson and minute taker MUST be assigned. The minute taking is to be a rotating role. At the beginning of each meeting the minutes for the previous meeting MUST be approved by a vote. Any minute change requests must be received 24 hours before the next meeting and the new version circulated 12 hours before the next meeting. The minutes of a meeting should be circulated to all team members and other stakeholders (if appropriate) within 48 hours of the meeting or 12 hours before the next meeting. The role of the minuter is as follows: 1) Record the attendees and non-attendees 2) Record the discussions 3) Record the decisions and votes 4) Record the actions 5) Update the status of the outstanding actions from the previous minutes 6) Ensure all agenda items have been covered 7) Write the agenda for the next meeting 8) Update PID (Project Inception Document) if necessary and redistribute 9) Record all in the minutes template and distribute 10) Take amendments to the distributed minutes and redistribute a new version 8
  9. 9. 8.0 Distribution of the Minutes The minutes of each meeting will be distributed by e-mail using the following format. (1) Subject: [PROJECTCODE]MEETING MINUTES: DD, DDD, MM, YY (2) Body: Date of Minutes: Minutes Overview: (main highlights and outstanding actions) Next Meeting DateTime: (if known) Next Meeting Location: (if known) (3) Attachments • Word 2007 version of minutes • Word 97/2003 version of minutes • PDF version of minutes9.0 Project Tools and Environments The agreed upon tools and environments for the project are given in the Project Tools and Environments section of this document. These standards MUST be adhered to by all any deviations from the standard must be put to a vote.10.0 Distribution of documents To ensure everyone can read the distributed documentation all electronic documents MUST be distributed in their native format plus PDF or JPEG (if an image)11.0 Tasks The result of all actions reviews MUST be a written presentation that is sent to all members of the team 12 hours prior to a meeting. The purpose of the written presentation is as documentation of the actionreview for the project diary.GroupCharter_ProjectCode_v1 Page 9 of 17
  10. 10. Team Organisation1.6 Project PhasesThe roles of team members are assigned at team meetings based on the project lifecycle phases. The primaryproject phases are as follows:Phase 1: Project InceptionPhase 2: Requirements Analysis and Functional SpecificationPhase 3: Development Sprint 1Phase 4: Development Sprint 2Phase 5: Development Sprint 3Phase 6: Acceptance TestingPhase 7: DemonstrationPhase 8: Documentation cleanupPhase 9: Project closure 10
  11. 11. 1.7 RolesThis table is a work in progress, as roles are assigned in project meetings the table will be updated.1.7.1 Phase 1: Project Inception Phase Role NamePhase 1: Project Fabrizio Valerio Covone ManagementProject Inception Analysis Stephen Carberry/Cara Murphy Design Shane Ellis/Christopher Conlan1.7.2 Phase 2: Requirements Analysis and Functional Specification Phase Role NamePhase 2: Project Fabrizio Valerio CovoneRequirements ManagementAnalysis and Analysis Stephen Carberry/Cara MurphyFunctionalSpecification Design Shane Ellis/Christopher Conlan Development Stephen Carberry/Cara Murphy Testing Shane Ellis/Christopher ConlanGroupCharter_ProjectCode_v1 Page 11 of 17
  12. 12. Communication Plan1.8 Project TeamCommunication between team members will be via e-mail, skype – chat voice and meetings. The teamdetails are provided below: Name DetailsCara Murphy E-Mail: cara.murphy@mydit.ie Phone: 087 097 5883Fabrizio Valerio E-Mail: fabrizio.covone@mydit.comCovone Phone: 085 233 1563Christopher Conlan E-Mail: Christopher.Conlan@mydit.ie Phone: 086 303 5531Shane Ellis E-Mail: Shane.Ellis@mydit.ie Phone: 087 940 4350Stephen Carberry E-Mail: Stephen.Carberry@mydit.ie Phone: 087 267 1183 12
  13. 13. Project tools and environment1.9 Project ToolsThe following software tools will be used throughout the project: Tool Name & Version PurposeMicrosoft Word 2007 All project documentation including minutes, requirements spec, etc will be kept and distributed in this format. For the purposes of backward compatibility a Word 97/2003 formatted and PDF version of the documents will also be saved from the most current version and distributed. All changes to the documents MUST take place within the MS Word 2007 environment with change tracking on.MS Project For documenting and maintaining the project plan.PDF995 Creates a PDF printer that allows any software print out to be converted to PDF. http://www.pdf995.com/1.10 Proposed Development EnvironmentGroupCharter_ProjectCode_v1 Page 13 of 17
  14. 14. 1.11 Document naming standardsDocuments are named as follows: Document Type Naming conventionMinutes YYYYMMDD_MeetingMinutes_ProjectCode_vDocVersionNumber So for this project the format is as follows YYYYMMDD_MeetingMinutes_ DSAGRP01_vXX Where the version number is an integer that increments. Example 20071210_MeetingMinutes_ DSAGRP01_v1 20071210_WorkshopMinutes_ DSAGRP01_v2Documents DocumentName_ProjectCode_vDocVersionNumber So for this project the format is as follows DocumentName_ DSAGRP01_vXX Where the version number is an integer that increments. Example Specification_ DSAGRP01_v1.docxProject Plans YYYYMMDD_PP_Note_ProjectCode_vDocVersionNumber So for this project the format is as follows YYYYMMDD_PP_Note_ DSAGRP01_vXX Where the version number is an integer that increments. Example 20071207_PP_FirstCut_ DSAGRP01_v1 14
  15. 15. 1.12 Project Filing structureGroupCharter_ProjectCode_v1 Page 15 of 17

×