The Agile Manifesto details some fundamental agile philosophies, one of which is a preference for Empirical Process control — which maintains that knowledge is derived from experience and decision making is based on what is known. Scrum is an Empirical Process based on inspection, adaptation, and transparency. gave the name “Agile” to the movement.
Continue readingWhy Scrum: Defined Process vs Empirical Process
Most software development projects are considered complex and unpredictable in nature due to the convergence of three factors: people, requirements and technology. The various approaches used for delivering and managing projects could be more easily understood in the context of process control models and project complexity.
Continue readingTraditional to Scrum Team — Forming, Storming Norming and Performing
The forming–storming–norming–performing model of group development was first proposed by Bruce Tuckman in 1965, who said that these phases are all necessary and inevitable in order for the team to grow, face up to challenges, tackle problems, find solutions, plan work, and deliver results. The theory remains a good explanation of team development and behavior.
Continue readingThe Best Agile and Scrum Resources and Links (2019)
Scrum is the most popular subset of agile. It is not only a lightweight agile development process framework, but also the most widely used framework. Here are the most basic agile and scrum resources for agile and scrum practitioners
Continue readingProject Management — Planning Phase: (11 of 12) — Communications Plan
Learn how to develop a Communications Plan. Lists the information needs of stakeholders, and describes how these needs can be satisfied through appropriate communications activities.
Continue readingProject Management — Planning Phase: (10 of 12) — Procurement Plan
Learn how to develop a Procurement Plan. Identifies how project needs can best be fulfilled by procuring products and services outside. Procurement Plan describes how the various aspects of procurement will be managed from the beginning to the end of the project.
Continue readingProject Management — Planning Phase: (9 of 12) — Change and Configuration Management Plan
Learn how to develop Change and Configuration Management Plan. Changes must be vetted and managed to ensure that they are within the project scope and are communicated to all stakeholders. This document identifies the project components that are governed by the change control process, and the documentation of change process.
Continue readingProject Management — Planning Phase: (8 of 12) — Risk Register
Learn how to log project risks with Risk Register, which is log of all identified risks that shows the probability and impact of the risks to the project, mitigation strategy, and when the risk is estimated to occur.
Continue readingFREE Online UML Tool
Visual Paradigm Online (VP Online) Express Edition a is free online graphing software developed for the community. Draw free diagrams with easy-to-use online drawing tools without watermarks and limitations such as number of diagrams, project file size, etc. You own the diagrams created for personal and non-commercial purposes.
Continue readingProject Management — Planning Phase: (7 of 12) —Project Risk Management
Learn how to develop a Risk Management Plan. Risks have negative impacts to a project. Therefore, it is important to take appropriate measures to identify, mitigate, manage and control them. Risk Management Planning is to identify and detail these aspects.
Continue reading