Lessons Learnt – The Retrospective

The Concept of a Retrospective (a Lessons Learnt meeting) should be familiar to anybody Working on an Agile Project. The Concept should be familiar to anyone who has actually Worked on any sort of Project. There have been a number of different names over the years that explain this activity. The activity of Reviewing what…

Sprint Retrospective and Continuous Improvement

A Sprint Retrospective Meeting can be one of the most effective activities you can use in an Agile Project. The Concept of Retrospectives is not new to Agile Project Management,. “Lessons Learnt” and “Post-Mortems” are Retrospectives and are typically held at the end of a Project. Kinds of Sprint Retrospective Generally, in Agile Environments a…

Task Estimation & Committing to User Stories

Task Estimation in essence starts with the Software Development Lifecycle taking a germ of a concept in somebody’s mind. This germ is then fleshed out, estimated and then translated into something Deliverable and executable. This journey, where the concept is Captured, explained, Refined and translated, is the magic of Software Development. In Scrum, part of…

Scrum Framework – Spreading Scrum in the Business

For those of you who are unfamiliar to the Scrum Framework, we are not talking rugby. Although the term is borrowed from the Game. Scrum is a Framework used in Agile Development. Iit is something your IT Business system “does”, unless they are still using Traditional Project Management for their Projects. Now you know that…

Cross-Functional – The Scrum Development Team

The Cross-Functional Scrum Development Team is puzzling to anyone who originates from a standard IT background; there are no architects, Business Analysts, Testers or UX Specialists, there are just Developers. This does not mean that there is no Business analysis, Software architecture design or system Testing. All the abilities required to finish the Scrum are…

Burndown Chart – Optimising Product Delivery

In an earlier article, we discussed the value of the Minimum Viable Product (MVP) in optimizing Product delivery. This was discussed both from the Pre-Project perspective and from Management of the Product Backlog. There are several tools and strategies that can be used throughout Development that will keep the Team focused and on track. These…

Stakeholder Involvement in Scrum

One of the Benefits of embracing any Agile Framework is the acknowledgement that the Stakeholder is an integral part of Product Development. If Customers are included throughout the journey towards an ended up Product, their Confidence level will increase as the Project advances. Likewise the will be able to intervene where the Product is diverging…

Earned Value Analysis for Project Management

One of the difficulties of Project Management is figuring out whether a Project is providing the anticipated Value. This problem can be solved through Earned Value Analysis while the Project is in development. Throughout the 1960s, the U.S. Department of Defence Developed a strategy called PERT (Project Estimation and Review Technique). Together with CPM (Critical…

Refactoring in Scrum – Is it Necessary?

Refactoring is the rather unknown term used to describe the activity of optimising Software Code. In the early days of Software Development, Refactoring was a given. Storage was pricey and inefficient Code was slow and vulnerable to error. The genuine Value of improving the Code base comes when someone has to maintain the Application. This…

Risk Mitigation – Managing Risk in Scrum

While Agile and Scrum are particularly targeted at lessening Risk (Risk Mitigation). This does not mean that Risk to any Project can be neglected. The Risk Management process explained has much in common with the majority of other Risk Management Frameworks. If your Company has adopted a specific Framework, it is advised that you line…