|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/agilefoundations/
课程评论：没有评论
课程名称：成为敏捷：从初学者到专家课程（零到英雄） 课程概述：您是否希望构建更优秀的软件产品？想成为一名高效的软件开发领导者？想参与并构建可持续发展的组织？如果您的回答是“是”，那么这个课程就是为您准备的。敏捷性是每个成功软件产品、团队和公司的核心。提升敏捷能力是您在软件开发职业成功与否之间的关键。本课程将教授您敏捷宣言的四个价值观和十二条原则。 课程结束时，您将能够理解并应用以下原则： - 构建有价值的软件 - 鉴别更优质的团队成员 - 享受工作 - 建立可持续的商业模式 适合人群：该课程面向软件开发公司的各类成员，包括软件开发者、软件项目经理、产品经理、Scrum Master、组织领导者、团队负责人以及信息技术的新手。 在软件开发的早期阶段（1980-2000年），软件的开发过程仍然像物理产品一样，采用了传统的工业项目管理技术，通常称为瀑布模型。然而，这种管理技术存在许多缺陷，例如在整个生命周期内没有产生可工作的软件，导致“应用开发危机”或“应用交付滞后”。这个过程通常需要近三年的时间，而在快速变化的软件行业中，这段时间过长，需求、系统甚至整个企业都有可能在这段时间内发生变化，导致之前的工作变得无用。 随着时间推移，软件业开始转向敏捷开发方法，以适应不断变化的需求，提供更灵活和高效的解决方案。本课程将详细介绍这一转变的背景和敏捷开发的重要性。 更多课程内容敬请期待…
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 developersSoftware Project ManagersProduct ManagersScrum MastersOrganizational LeadersTeam LeadsManagersFreshers In Information TechnologyIn 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.No working software is produced until late during the life cycle.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.High Risk and Uncertainty.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.Cannot accommodate changing requirements.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...
