2015 Software Development Software Review 
Rebel’s Guide to PM
APRIL 2, 2022
The APM Planning, Scheduling, Monitoring and Control Guide (2015) defines rolling wave planning as ‘the planning density that is achieved at different moments in time. As the team undergoes the work, the project manager can constantly review the schedule and add more detail to the next waves as this is known. Then review the next wave.
Scrum.org
AUGUST 25, 2022
Clinical burnout is a very severe condition that can put people out of work for the rest of their lives and is often indistinguishable from clinical depression (Bianchi, Schonfeld & Laurent, 2015). For example, I (Christiaan) love the thrill of solving a hard coding problem. Burnout–depression overlap: A review. References.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
AUGUST 17, 2020
Initially coined by cognitive psychologist Lee Ross (1977), it happens when people underestimate the influence of the situation on the behavior of others while overestimating the influence of their personal traits and beliefs (Berry, 2015). Standish Group, 2015). Vol 5(1) 2015. Psychological Review, 94 (2), 211–228.
Kiron Bondale
MARCH 27, 2016
I wrote an article in October 2015 describing how the eight forms of waste (a foundational lean tool) can affect project teams. An example of this might be a software developer who continues to refine the design or code for a module even when it successfully passes usability, functional and performance tests.
Project Risk Coach
AUGUST 1, 2016
The CHAOS Reports have been published every year since 1994 and are a snapshot of the state of the software development industry. The Standish Group 2015 Chaos Report studied 50,000 projects around the world, ranging from small enhancements to massive systems implementations. Who are your stakeholders?
Scrum.org
JANUARY 25, 2021
The reasons for this are apparent, with software eating the world and the pace of innovation accelerating as the market-entry barriers of the technology sector are continuously lowered. This autonomy is mostly awarded within the product delivery organization to create software or other technology-related products and services.
Scrum.org
FEBRUARY 25, 2020
When I started using Scrum as a software developer back in 2007 I noticed that this new ways of working really worked, then I decided to learn more about and I became a Scrum Master in 2012 and in 2015 I started to teach Scrum, overcoming my fear of public speaking. I will explain the peer review at the end of this article.
Expert insights. Personalized for you.
414 
Let's personalize your content