IT 415 Short_Paper__Detailed_Design_Documents.docx Detailed Design Document 6-2 Short

IT 415 Short_Paper__Detailed_Design_Documents.docx    Detailed Design Document  6-2 Short Paper  IT-415  I will be starting with the WBS (Work Breakdown structure) diagram that will organize all the tasks into sections to reduce the possibility of overwhelming the developers. This will also lay out a clear path that must be followed and allow us to stay on track with development of the new application. The flow of this will be breaking the project down into 5 phases that will then each be broken down into sub phases or tasks to be completed during that phase. This will also give something for the stakeholders to reference when keeping updated with the projects progress and where the team is at in the development of the application.   A timeline will also be provided to outline each of the expected timetables for the WBS document that will give stakeholders a better understanding of what is expected for the development of this application. This will be a detailed estimation of the time it will take to complete each of the phases and sub phases/tasks.  If I had additional time to research and plan id like to include a full backlog for the project. The backlog would use information from the WBS and timeline to layout full detailed task list for each sprint. This would incorporate detailed tasks in the Jira application using the Kanban style of development, for example GB-0123 œUpdate development DB for new UI form acceptance Blocked by GB-0122 œfinish UI design and accept changes to form section. Each task will have a details