The Work Breakdown Structure (WBS) is used in both the traditional (predictive) environment and the agile environment. The first article explains the basic WBS.

The Ultimate Guide to

Work Breakdown Structure (WBS)

Brought to you by ProjectManager, the project management software that incorporates WBS into their features.

Work Breakdown Structure (WBS) in Traditional and Agile Life Cycles with MS Project

The second article above explains the difference between the traditional WBS and the agile life cycle WBS. Once you understand the difference by reviewing the examples, you will create two WBS - one for the predictive cycle and one for the agile cycle - as shown in the article above. Recreate these diagrams just as you see them.

This time you'll be creating two different kinds of Work Breakdown Structures (WBS). Perhaps you're familiar with them? If not, this will be an opportunity to explore. Create a traditional WBS and an Agile WBS. You will see the examples in the article provided depicting a book release, now use that information and translate it to one of the following scenarios:

• Create a new app to assist with parking availability on campus
• Create a new job posting site for students
• Implement a new QR code application to track and trace students from arrival to departure
• Install self-service vending machines on campus with AI capabilities to pull food/drink off the shelf and automatically charge your school account

You'll need to consider all of the things that would go into a project like that and start to break it up into work categories. Remember, the WBS is not a task list, it's an outline of the various buckets of work that need to occur.

Remember to create an account at lucidchart.com (if you haven't done so already). You can create both charts on one document - they don't need to be separate.