Agile Project Management: How to build anything Digital

The Objectives of this Course are:

• Understand the difference between Waterfall and Agile Software Development

• Define the Roles and Responsibilities of an Agile Development Team

• Get to know the Software Development Lifecycle (SDLC) from beginning to end

• Internalize the importance of regular Customer Testing and adapting your Product accordingly

We will be covering 3 key themes:

Theme 1 – Software Development Project Management Approach: Waterfall vs Agile

Waterfall and Agile are the most prevalent methodologies of processes. Waterfall is a sequential methodology where tasks are handled in a mostly linear process. Agile, on the other hand, is an iterative methodology which incorporates an iterative and collaborative process. Selecting the right methodology for your projects will depend on preference and the nature of each project. We will have a look at both.

Theme 2 – Your Agile Cross-Functional Software Development Team

The Agile cross-functional team is comprised of the Scrum Master, Product Owner, Developers, Business Analyst, and Designers, to name just a few. They all come with a minimum definition of responsibilities and accountability to allow teams to effectively deliver work. Her we will have a more detailed look at each of them, without forgetting the crucial emphasis on your Customer.

Theme 3 – The E2E Agile Software Development Lifecycle

By adapting an Agile software development life cycle (in short, SDLC), you will benefit from an iterative approach to the design, development and testing of your software feature. We will have a more detailed look at each stage that your feature undergoes: from its initial ideation phase and fleshing out the initial requirements, to the actual build development and testing phases, prior to launching the product to the customer market

By the end of this course you will:

• Know the difference between Agile and Waterfall Software Development

• Learn about the benefits and drawback of each methodology

• Be aware of typical Agile meetings to use in your daily work life: Sprint Planning, Standups, Demos and Retrospectives

• Understand the key roles and responsibilities of team members

• Recognise the importance of regular collaboration with your customers

• Able to explain each phase of the Agile Software Development Lifecycle

• Be confident in kicking off an ideation phase or initiating a creative process

• Understand what it takes before any code development takes place – from writing requirements to sketching out designs to planning the technology infrastructure

• Be mindful of the importance of regular testing of your software, both in a a manual as well as automated way

• Know how to launch your application to friends and family

• Be a champion in gathering feedback from your customer, and iterating your product accordingly, to improve and launch quicker and more successfully