2002 Agile Software Engineering 
Scrum.org
OCTOBER 19, 2022
What is the business case for Agile teams? We think we do well to base our beliefs about Agile more on evidence. This post is our attempt to bring an evidence-based perspective to the business case of Agile teams. Each post discusses scientific research that is relevant to our work with Scrum and Agile teams.
Scrum.org
FEBRUARY 3, 2020
Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. Why our brain is not built for software engineering. It is a mental process and a limited mental resource (Ashcraft, 2002). Cognitive paradigms, applied to Scrum / Agile. This will not work.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MARCH 11, 2017
This is the motivation for short work intervals found in agile development. . Mazzuchi, and Shahram Sarkani, Systems Engineering , Volume 17, Issue 4, Winter 2014, Pages: 375–391. Hybrid–Agile Software Development Anti–Patterns, Risks, and Recommendations,” Paul E. The probability of something happening.
Herding Cats
OCTOBER 5, 2018
Little [8] makes the claim that agile methods don't follow the Cone - that is the uncertainty doesn't reduce as the project proceeds. A Quick Estimation Approach to Software Cost Estimation," Leckraj Nagowah, Hajrah BibiBenazir, and Bachun, African Conference on Software Engineering and Applied Computing , . "A
Leading Agile
JUNE 18, 2018
People who specialize in testing software will need technical skills more-or-less on par with competent software engineers. In a 2002 piece entitled The Law of Leaky Abstractions , Joel Spolsky observed that abstractions over any implementation can leak details of that implementation. Contracts vs. Promises.
Epicflow Blog
MAY 14, 2019
Donato Piccinno , a Project Manager at DXC Technology, advises to “measure and improve clarity, unity and agility. Facts and Fallacies of Software Engineering by Robert L. Glass ( Addison-Wesley Professional, 2002), also recommended by Giorgio Locatelli. Such an approach is all about being proactive rather than reactive.
Herding Cats
APRIL 13, 2018
This is the same paradigm of Agile software development where responding to change over following the plan is part of the original manifesto. Managing Requirements for Business Value," John Favaro, IEEE Software , March/April 2002. Aligning Software Investment Decisions with the Markets ," Hakan Erdogmus. "
Expert insights. Personalized for you.
225 
Let's personalize your content