Students will read the assignment narrative, and construct a project work breakdown structure document, using Microsoft Word. Then, students will paste the work breakdown structure into a new Microsoft Project file. Both the Word file and the Project file should be submitted.
Students will read the assignment narrative, and construct a project work breakdown structure document, using Microsoft Word. Then, students will paste the work breakdown structure into a new Microso
CIS 366 Stackhouse Module 5 Work Breakdown Structure Assignment Page 1 Module 5 Work Breakdown Structure Assignment This assignment is to put some serious thought and effort into constructing a Work Breakdown Structure for the time tracking system for Nuts and Boltz. B ased on your financial analysis which indicated tha t the Linux platform offered the most value, Linux wa s chosen as the platform of choice. The hardware vendor has indicated that they will ne ed an approximate 3-month lead time in order to deliver the server. Once the server has been insta lled at Nuts and Boltz, a Unix-based version of Oracle will then be installed and the server should be rea dy for the new application software whenever it is completed. Part 1 – Create Work Breakdown Structure Outline in MS Word Format The company has worked with a third-party developer who will perform the development of the new software. The development vendor will be responsib le for database schema, physical design and deployment; application software writing; the creat ion of the conversion software to populate the initial data set with historical data; and all associated d ocumentation. The graphical design of the user interface will be provided by the Communications De partment at Nuts and Boltz, to ensure that it is consistent with corporate standards. Communication s guarantees that their pieces will be completed prior to the completion of the application software , but after a prototype of the system is finished. Once the user interface has been designed, Integrat ion programming and testing will need to take place to combine the UI and “back end” code of the applic ation. The result will be one consolidated beta system. Nuts and Boltz IT staff will test the software inte rnally first and then it will be rolled out to a test group of computer-savvy engineers and supervisors to ensu re correct results. From this pilot test, the software usability will be judged, and any feedback provided will be consolidated back into the software product. Obviously the earlier that the feedback c an be garnered, the better, e.g. we don’t want to w ait until we think we’re done to realize that we’ve mis sed the target. The project also needs to ensure that enough time is set aside to allow for adequate cycl es of this testing feedback redesign until the final version of the product has been completed. Nuts and Boltz salaried workers need to start using the new system at the start of the new fiscal year, which is only 6 months away. By now you should have an idea of what it really ta kes to build a software system. You know the corre ct work to write code (analysis, design, flowcharting, prototyping, et cetera). You know that databases are built up by generating ERD diagrams, thinking about cardinality and normalization, and then generating schemas. What we’re talking about here is the “rig ht” way to build systems, using the proper tools and techniques. You will have to tie together all of t he techniques and knowledge you’ve gained from your other major classes along the way. The majority of your grade will be based on how det ailed your WBS is and how much thought you’ve put into it. Think about the deliverables of the proje ct and put them on the WBS as needed. You might CIS 366 Stackhouse Module 5 Work Breakdown Structure Assignment Page 2 want to organize the WBS around the feasibility/bus iness case, analysis, design, implementation, closing model. I’ll leave the actual organizing to you, bu t I think that best parallels how you’ve been taugh t to approach development. You want to make this detailed! Don’t think that 2 0 items is enough. Enough is when you have a well- defined WBS. I’d start with something like this: 1.0 Initiating 1.1 Build business case with proposed solution for the new time tracking system, performing financial analysis 1.2 Get feedback on business case from fellow ITS staff 1.2.1 Deliverable: business case 1.3 Make presentation to administration selling the bus iness case 1.4 Determine project manager 1.5 Determine stakeholders and requirements 1.5.1 Deliverable: stakeholder register 1.5.2 Meet with stakeholders for project input 220.127.116.11 Deliverable: requirements matrix 1.6 Meet with project manager to compose the rest of th e project team 1.7 Build the project charter 1.7.1 Deliverable: project charter 1.8 Kickoff meeting 1.8.1 Schedule kickoff meeting 1.8.2 Deliverable: calendar date for meeting and agenda 1.8.3 Hold kickoff meeting 18.104.22.168 Deliverable: meeting minutes You get the idea, and this was just part of the ini tiating stage! Reading over the book (especially chapters 2, 3, and 4) provides a sample case study with some of the supporting documents. The chapters also looked at each of the knowledge areas , talked about what we do in each one and what the outputs are (which often become deliverables). There is no need to go decompose the requirements m ore than 3 levels. Use what you know about creating software along with your imagination for t his WBS. Part 2 – Insert WBS In MS Project Now that you’ve developed a complete work breakdown structure outline, now copy that structure into a new MS Project file, and submit that file as part of the assignment. No, this isn’t a quick assignment, but it’s not nec essarily a difficult one either. It’s more of an exercise in determining what needs to be done on a smaller size project.