Articles
When an organisation is trying to adopt Scrum, this is the biggest question that comes in their mind. Since traditionally the Scrum suggests that the Scrum Teams should ideally be 6-8 Member team, how will this work for humongous projects which have huge team some time in 100’s. This leads to a misconception that Scrum…
Scalability of a process, network, or unit is its ability to adjust or adapt to any expansion. For example a central server is said to be scalable if it performs similarly when attending on either five clients or fifty clients. In Scrum, it means that the scaling mechanisms applicable for a single Scrum Team can…
Relative values are used for story points estimation instead of absolute values. This approach renders it quite simple enough to create these kinds of estimates while facing uncertain situations. With experience and time, Scrum teams will develop the capability to sharpen up their estimates for more precision. They can figure out the number of story…
Technical debt — also referred to as design debt or code debt — refers to the work that teams prioritize lower, omit, or do not complete as they work toward creating the primary deliverables associated with the project’s product. Technical debt accrues and must be paid in the future. Some causes of technical debt can…
Scrum Team, also referred to as the development team, is responsible for developing the product and they possess all the essential skills required to carry out the work of the project. They have a high level of collaboration to maximize productivity, so that minimal coordination is required to get things done. To minimize dependency, team…
Scrum originated from the activity related with the passage of ball among rugby players swiftly. The designing of scrum was such as to deal and manage fast changing necessities of the software industry. It is one of the various frameworks of Agile Software Development used in the delivery of functional software with visible results towards…
The iterative product development involves developing the product in small portions and receiving the customer feedback/review at the end of each portion. This method is particularly useful in software development projects and is one of the basic principles of Scrum methodology. The concept is, more quickly you deliver the product to the user, the quicker…
Being an active member of a couple of IT projects and regularly attending hours of daily scrum meetings today I am overwhelmed to share my thoughts about it. An integral part of the Scrum process is the Daily Scrum meeting which is a regular ritual practiced every morning. The team comes together on each working…
In October of 2013, CIO.com published an article by Jennifer Schiff titled “7 Top Wishes of IT Project Managers.” Even though it is directed to IT professionals, the list—based on their research—undoubtedly meets with little or no argument from experienced project managers everywhere. From being brought into a project after important decisions that really needed…
Risk is defined as an uncertain event that can affect the objectives of a project and may contribute to its success or failure. Risks with a potential for positive impact on the project are called opportunities, whereas threats are risks that could negatively impact a project. Managing risk must be done proactively, and it is…
