Tthe Project Management Workbook (PDF)

Added on - 24 Mar 2021

  • 23


  • 4088


  • 9


  • 0


Trusted by +2 million users,
assist thousands of students everyday
Showing pages 1 to 6 of 23 pages
Using the DocumentThis document provides a set of templates for the Project Management Workbook to besubmitted as Assessment for the course of Software Project Management.The content is based upon the appropriate International Standards for Software ProjectManagement Documents.These templates should be considered the minimum level of detail required for theWorkbook.It is expected that you would conduct further research into relevant materialthat may be required in each section.Items that are intended to stay in as part of your final document are in bold; italic text isused for explanatory information that should be removed when the template is used.At the top of each workbook section is a table. This table records who has worked on eachsection, and the work that they have contributed. This table must be kept up to date as thesections are completed, and the entire team must agree to the content of the table.Sections 1-7 are planning documents that you complete based on the project you havechosen. Section 8 of the workbook is a post project review based on your work over thesemester, and this section of the workbook refers to the development of the workbookitself,NOTthe project you chose.In order to complete this section you will need detailsrelating to how your team conducted themselves in building the workbook, as well as theplanning material from section 9.Treat the workbook development as a project.Section 9 covers the project planning for your workbook. Each team member needs to keepa weekly timesheet detailing time spent and tasks completed in this section.This is wheretasks may be allocated and tracked, and individuals can enter timesheet information. Thissection must be maintained from the beginning of the project
1.Project CharterRevision HistoryDateVer.AuthorAddition/Alteration12/02/201.0Fasiha Fatima12/03/201.0Fasiha Fatima1.1 Company InformationProject Title:E-DonationProject Manager:ZainAbbasCompany Name:TechTreeTeam Members:FasihaFatima(17-SE-25)MuhammadHamza(17-SE-43)ZainAbbas(17-SE-103)Business Experience:Our company is working since 2019.It is an international company.Project Description:Our project(app) is a platform to donor and beneficiary for makingdonation process easier and reliable. Due to Covid-19 ,there is a difficulty for the people tomake donations because have to maintain social distancing .This app will help them to givedonations online .People can give charity or donate to poor e.g. clothes, extra furniture, toys,extra cooking wares and money etc through our application. Through this application peoplecan able to find needy people so they could donate things and money of Zakat and Sadqa. In
this application people who know and trust each other will share the details of a needyperson. So that anyone from the group who wants to help can contact that needy person andcan help them through money or things.Our project E-Donation is a social welfare mobileapplication. With the help of this application people will make donations easily and directly.Project Objectives and Success criteria:Project ObjectivesSuccess CriteriaPerson ApprovingScope:Milestones areRequirement phaseDesign phaseDevelopment phaseTesting phaseProject manager willmeasure the performance byusing the AON,AOA andGantt chart techniques.Project SponsorTime:Goals are:Provide a user-friendlyinterface for the donor.Provide easier andreliable ways to makedonations based onsocial trust.Directly involve thedonor in the process toimprove transparency.Enable users toorganize online charityevents.Suggestpotentialbeneficiaries to donorsand bridge the gap ofcommunicationbetween themOn Fridays of every weekperformance will bemeasured and gap will befounded and then covered.Project SponsorCost:Budget ranges from 5000 to6000.Google Play ConsoleAccount(3500 to 4000)Logo Designing (1500 to2000)Rupees will be the currencyProject Sponsor
Other:All features should beaccording to the need ofstakeholders ,providing extrasatisfaction to the users.Performance will bemeasured in terms ofplanned cost and time.Project SponsorApproach:We are using agile model for this project. Agile model’s phases are different from simpleSDLC .Requirement AnalysisDesignCoding and developingTestingDeploymentMaintenanceAgile has become the go-to framework for helping app startups and development agenciesmaintain a focus on delivering a quality app quickly and efficiently. Agile maximizes valuethroughout the development process and significantly reduces the overall risk of a project.Agile model is best for our android application(E-Donation).Agile model is being usedbecause of following reasons:1. Quality ProductIt was common to test software before launch, but with Agile, testing is integrated throughoutevery stage of development to ensure a quality end product. Continuous testing allows roomfor adjustments and can catch issues and bugs before they manifest.2. Faster Time to MarketSprints play a major role when working Agile. These set periods of time allow teams todeliver frequently and rapidly.Speed is key for startups.
3. FlexibilityFlexibility is praised as one of the most beneficial reasons to use Agile. Because themethodology allows for change, there is always room for mistakes and opportunity to iterate.4. Cost EffectiveBecoming more Agile is proven to save money, and most importantly, it helps to invest fundswisely.5. People Focused/CollaborativeAgile puts a strong focus on people and collaboration, Which provides the development teamwith many opportunities to work with the client and understand their vision.6. Reduced RiskWorking on small tasks that build up to the big picture will help you identify issues early.Reducing risk and making it easier to respond to any changes.7. Enjoyable Work EnvironmentInstead of team members and clients working in complete isolation for hours, everyone will beworking together to deliver a quality end product. Workshops, brainstorming sessions, andmeaningful conversations are all part of the development process.8. User FeedbackIn most cases, Agile utilizes user stories to determine product features. When you create userstories, you’ll focus on solving the real needs users have, instead of developing features thatcould turn out useless.
9. Quick Decision MakingWorking under set deadlines and timeframes will force you to be on your toes at all times.This applies to decision making as well, because you won’t b to sit down with your team toagree on every decision.10. Results DrivenInstead of focusing on the process itself, team will be driven to achieve milestones andresults.Stakeholders:Sr. noStakeholders1.Client2.User3.Consultants4.Core Team5.Marketing people6.Adjacent Systems7.Technical Experts
You’re reading a preview
Preview Documents

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Download This Document