Becoming Agile: Beginners To Expert Course (Zero to Hero)

Description

• Do you want to build better software products?

• Do you want to be an effective software development leader?

• Do you want to build and be part of sustainable organizations?

If YES, Then this course is for you. ??

At the heart of every successful software product, team, and company is AGILITY. The ability to be agile is the gap between you and success in your software development career.

In this course, I will teach you the 4 values and 12 principles of the Agile Manifesto.

At the end of this course, you will understand principles that will help you

• Build valuable software.

• Identify better team members.

• Enjoy your work.

• Build a sustainable business.

Who is this course for? It's for members of software development companies.

• Software developers

• Software Project Managers

• Product Managers

• Scrum Masters

• Organizational Leaders

• Team Leads

• Managers

• Freshers In Information Technology

In the early days of software development (1980-2000), software was still being developed like a physical product because they inherited industrial project management techniques. Requirements come first, the design comes second, then development, then testing and so forth. This was called the waterfall model - think a slow, trickling, stage-by-stage process.

Under Waterfall, the software project is rigorously designed upfront, in the way that one might manufacture a wristwatch or a car. In a waterfall model, each phase must be completed before the next phase can begin and there is very little overlapping in the phases.

However, this kind of project management technique had many flaws.

1. No working software is produced until late during the life cycle.

   1. Software development experts referred to it as "the application development crisis," or "application delivery lag" estimating that the time necessary to go from idea to a complete product was almost 3 years.

2. High Risk and Uncertainty.

   1. 3 years is a long time in the software world. A lot can change in just 6 months- requirements, systems, and even entire businesses were likely to change-making your work of the last 3 years obsolete.

3. Cannot accommodate changing requirements.

   1. Not a suitable model of development for complex projects with a high risk of changing requirements. For example, once an application is developed and is in the testing stage, it is very difficult to go back and change something that was not part of the original plan. When things needed to be changed, we need to start from the top all over again, further increasing the time to deliver the software.

That's when the world pivoted to AGILE.

More in the course...

TAKE THIS COURSE