Assume you were the project manager of a new software project developing our university's online application processing system. Develop a WBS table based on the traditional software development life cycle and a hierarchical WBS for agile methodology.

In your traditional WBS, clearly (and reasonably) specify task ID, task name, duration (in days), and precedent task(s). You must use a number coding (1, 1.1., 1.2.,...) to represent task levels. Identify at least five tasks for Level 1 (1, 2, 3,...); identify at least three tasks per level 1 for level 2 (Level 1.1, 1.2, and 1.3); and identify at least three tasks per level 1 for level 2. Try Level 3 (1.1.1, 2.1.1, 3.1.1) for extra points. In developing your agile WBS, consider the characteristics of agile development (SCRUM). Task name, dependency, and duration are needed. (40 pts.)

Hierarchial agile WBS (25 pts.)