Scrum.org

DECEMBER 18, 2020

The book “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle (2002). The book “Agile Project Management with Scrum” by Ken Schwaber (2004). The book “The Enterprise and Scrum” by Ken Schwaber (2007). The Scrum Guide” by Ken Schwaber and Jeff Sutherland (2009, 2010).

2010 231

2010 SCRUM 2002 2004 231

nTask

JANUARY 21, 2019

Professionals do not come with a manual so how should Agile teams work in collaboration? What may seem like a completely different ballgame, if studied closely, just may be able to teach Agile teams a thing or two. A renowned athlete, Trotter won her first Olympic gold medal in the 2004 Olympics.

Underperforming Technical Team 98

Underperforming Technical Team Agile 2012 2008 98

Scrum.org

MAY 26, 2020

TL; DR: The Agile Movers & Shakers Interview w/ Christiaan Verwijs & Barry Overeem. If so, you can subscribe here and join 26k agile peers. The Agile Movers & Shakers Interview with The Liberators Christiaan Verwijs & Barry Overeem. What brought you to ‘agile?’. From there, a lot of what we call “Agile” makes much sense.

Agile 99

Agile 2004 SCRUM Software Developers 99

The IIL Blog

AUGUST 8, 2023

Articles are now appearing addressing burnout specifically in a project management environment [Verma (1996), Haynes and Love (2004), Richmond and Skitmore (2006), Pinto et al., 2014), and Jugdev et al., There are more options available for correcting project work-related issues. REFERENCES Freudenberger, H. Staff burn-out. Haynes, N.S.,

Underperforming Technical Team 78

Underperforming Technical Team 2004 2005 2006 78

Rebel’s Guide to PM

JUNE 28, 2021

I took my first Practitioner course in 2004. It’s a predictive methodology, although PRINCE2 Agile allows for agile frameworks. PRINCE2 Agile came along in 2018 to enable PRINCE2 to work with agile concepts like timeboxing and Kanban. Who is PRINCE2 for? PRINCE2 works in a huge number of industries and domains.

Prince2 197

Prince2 Governance Government Certification 197

Scrum.org

MAY 29, 2020

If you’re not already aware, the way you think of testing within an agile approach is fundamentally different to the traditional one. Behaviour-Driven Development (est 2004). In 2004, the next discovery for Dan was the concept of business value and why we write software. But let us leave that for another day. He found: -.

Software Review 132

Software Review Technical Review 2004 2003 132

Gunther Verheyen

DECEMBER 17, 2020

In the end, the sources I used for describing the evolutions of the definition of Scrum are: The paper “SCRUM Software Development Process” by Ken Schwaber (1995, 1996) The paper “SCRUM: An extension pattern language for hyperproductive software development” by Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber and Jeff (..)

2010 141

2010 SCRUM 2002 2004 141

Herding Cats

OCTOBER 30, 2018

There have been some recent posts about managing scope, defining needed Features, determining how to release software to stakeholders - in both traditional and agile processes. This document is all but unknown in the Enterprise IT domain and completely unknown in the agile software development world.

Planning 109

Planning 2007 Technical Review 2009 109

Gunther Verheyen

JANUARY 27, 2021

In May 2004 I attended a CSM class (“Certified ScrumMaster”) by Ken Schwaber in Brussels (Belgium). In April 2010, at an event of the Agile Consortium Belgium in Brussels, I asked Jeff Sutherland about this new organization founded by his former companion. In October 2003 my life of Scrum started, albeit not with Scrum.

SCRUM 103

SCRUM 2012 2010 2011 103

Herding Cats

MAY 10, 2019

This blog page is dedicated to the resources used to assess risks, their impacts, and handling strategies for software-intensive systems using traditional and agile development methods. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010.

Risk Management 38

Risk Management Risk Technical Review 2002 38

Herding Cats

MAY 11, 2019

This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. 920, November 2004. 3 September 2004, Heiot Watt University, Association of Researchers in Construction Management , Vol. 255, April 2010. Talat Birgonul, and A.

Risk Management 35

Risk Management Risk Technical Review 2002 35

Herding Cats

DECEMBER 16, 2017

Here are some resources that will provide guidance to produce credible software development estimates, in both traditional and agile domains. While some have publication dates that may seem old, the principles in these books are immutable, even for agile projects. Agile Estimating and Planning , Mike Cohn, Prentice Hall, 2006.

Software Developers 46

Software Developers Software Development Estimate 2006 46

The IIL Blog

APRIL 27, 2018

Here are some examples of SMILEs that I began to create in 2004 in conjunction with my dissertation that focused specifically on project management. agile retrospectives). Risk: Uncertainties that may be encountered in implementation. Resources: Number of participants, software, and systems required, facilities, etc.

2004 121

2004 Software Review 2012 PMI 121

Herding Cats

MARCH 17, 2019

An Introduction to IMP/IMS , 17 Oct 2004. Agile Project Management. Agile Software Development for Government Software Intensive System of Systems (SISoS) , Boulder Agile Meetup, 27 July 2016. Integrating Agile Software Development with Earned Value Management , College of Performance Management, IPM Workshop, 2015.

2003 54

2003 2011 2008 Performance Measurement 54

ProProfs Project Management

JANUARY 15, 2021

Anderson was the first person to implement this kanban approach to project management to their IT, Software Development, and knowledge work in 2004. To become agile, it is important to implement the feedback loops. However, after 1940 David J. How Kanban Works. Make Feedback Loops Mandatory. Q4: Can kanban and scrum work together?

Software Review 81

Software Review Technical Review 2004 SCRUM 81

EasyProjects

SEPTEMBER 19, 2018

My team and I were running a software development company back in 2004 when we realized that our projects needed to be managed in a better way. Pavel has instilled a solid agile development process that tackles our small updates to extensive builds like developing our Artificial Intelligence strategy and capabilities.

Artificial Inteligence 40

Artificial Inteligence 2004 2015 Infrastructure 40

Leading Agile

MARCH 11, 2020

Agile Unplugged is your chance to explore LeadingAgile’s freshest ideas, mental models, frameworks, and solutions with the people that are actually doing the work of leading large-scale Agile Transformation, out in the field. What was that, probably 2004, or ’05 or something in that kind of range, I think?

Agile 105

Agile Fractional CTO CTO Hire Influencer 105

Herding Cats

MARCH 11, 2017

This is the motivation for short work intervals found in agile development. . Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects,” Dana Roberson and Mary Anne Herndon, 10 th Annual CMMI Technology Conference And User Group , November 5 – 8, 2012, Denver, CO. The probability of something happening.

2003 46

2003 2014 2015 2011 46

Gunther Verheyen

FEBRUARY 27, 2024

2) Jeff Sutherland, “Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies,” Cutter Business Technology Journal Vol. 5–11; and “Agile Development: Lessons Learned from the First Scrum,” Cutter Agile Project Management Advisory Service: Executive Update Vol. 20, 2004: pp. 1986, [link]. (2) 14, 2001: pp.

SCRUM 71

SCRUM 2004 Software Review 2019 71

Scrum.org

AUGUST 17, 2020

It happens, for example, when we don’t trust a certain person or group of people, and then only see behavior that fits with our belief (or even interpret it as such) without considering observations where they don’t (Oswald & Grosjean, 2004). 2004), “Confirmation Bias” , in Pohl, Rüdiger F. (ed.), Standish Group, 2015). Nisbett, R.

2015 219

2015 2014 2004 Influencer 219

The IIL Blog

JUNE 7, 2023

Typically, the owner does not care whether the team is prototyping or coding, or how many agile iterations they have worked through! Both parties adopt a new business-oriented framework for the life of the project and stop using the technical project lifecycle for business communication, which is not its design purpose. 3 Hornby, Robin.

2004 78

2004 2023 2017 Consulting 78

MPUG

DECEMBER 3, 2021

He joined Edwards in 2004 as a project coordinator and scheduler and provided project planning and scheduling support to variety of commercial and federal government clients. If you are using agile, you’re not going to necessarily have a lot of requirements at once. Walter’s certifications include the PMP and MCTS.

Software Review 52

Software Review Technical Review Underperforming Technical Team Risk Management 52

Scrum.org

JANUARY 27, 2021

This was the birth of the Agile movement with the Scrum Framework (1993), the Agile Manifesto (2001), and later Kanban (2004). Agile Manifesto, 2001. Instead of coming up with best practices, we realise that there are only good practices for the situation at hand. Today that is the people doing the complex cognitive work.

2001 212

2001 Software Review Technical Review Underperforming Technical Team 212

Herding Cats

JUNE 19, 2017

Misinterpretations of the “Cone of Uncertainty” in Florida during the 2004 Hurricane Season, Kenneth Broad, Anthony Leiserowitz, Jessica Weinkle, and Marissa Steketee, American Meteorological Society , May 2007. Here's some background on the topic of the Cone of Uncertainty. Each of these can be found with Google.

Technical Review 35

Technical Review Performance Measurement Underperforming Technical Team Estimate 35

Scrum.org

FEBRUARY 3, 2020

Scrum/Agile) are more suitable to deal with complex problems because they are more attuned to our cognitive abilities. Cognitive paradigms, applied to Scrum / Agile. 2004) _How can we think the complex?Retrieved Using the aforementioned cognitive limitations, I will argue that approaches based on a fully rational analysis (e.g.

2002 200

2002 SCRUM 2007 2003 200

Herding Cats

APRIL 4, 2019

Paul Chavas, Elsevier Academic Press, 2004. Agile Risk Management and DSDM Pocketbook , Alan Moran, IARM. Agile Risk Management and Scrum , Alan Moran, Institute for Agile Risk Management, 2014. Effective Opportunity Management for Project: Exploiting Positive Risk , David Hillson, Taylor & Francis, 2004.

Risk Management 43

Risk Management Risk 2003 2011 43

nTask

NOVEMBER 20, 2020

In 2004 this system was adopted by David J. Simply put, Kanban is an agile methodology and is a system for work management. Taiichi Ohno , an industrial engineer from Toyota Motors – Japan, is credited with creating the first Kanban system. He applied the method to the IT sector, SDLCs , and various knowledge-base platforms.

2004 60

2004 Engineering Agile Executing 60

Herding Cats

APRIL 16, 2019

Agile Project Management (#APM). Agile Software Development (#ASD). Integrating Agile and Earned Value Management (#AEVM). Agile and Earned Value Management Bibliography of papers, books, and thesis (#Biblio). Agile Project Management. Agile and all SW development operates in the presence of uncertainty.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Herding Cats

MARCH 11, 2018

By the way, the pure conjecture that agile enables late changing requirements to not have a significant impact on the cost and schedule of the development project is completely lacking any testable evidence outside of personal anecdotes of agile advocates. IEEE Transactions of Software Engineering, 1 (1984): 4-21. Charette, R.,

Software Developers 34

Software Developers Software Development Risk Management Risk 34

Herding Cats

MAY 7, 2019

This blog page is dedicated to the resources used to estimate software-intensive systems using traditional and agile development methods. Cost Modeling Agile Software Development,” Maarit Laanti and Petri Kettunen, International Transactions on Systems and Applications, Volume 1 Number 2, pp. 61, September 2004. Prakash and V.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

Review on Traditional and Agile Cost Estimation Success Factor in Software Development Project,” Zulkefli Mansor, Saadiah Yahya, Noor Habibah Hj Arshad, International Journal on New Computer Architectures and Their Applications (IJNCAA) 1(3): 942–952. Story Point Estimating,” Richard Carlson, ALEA, Agile and Lean Associates, 2013.

Estimate 64

Estimate 2006 2005 2013 64

Paymo App

SEPTEMBER 8, 2017

Launched in 2004, it’s aimed at giving you a better handle on your business and the work your teams are doing. There are no options for Kanban boards either, so teams used to Agile approaches could struggle. Basecamp is regularly in the lists of best project management tools, and for good reason.

Software Review 104

Software Review Technical Review 2017 2016 104

MPUG

MARCH 25, 2021

There may be a call for more of an agile approach than a waterfall approach, if you catch what I mean, quote, unquote. When I was making up this slide, once upon a time, I was actually thinking about one of the classes that I gave a while back and think it was around in 2003, 2004, and it was for Help Desk administration.

Technical Review 52

Technical Review Underperforming Technical Team Risk Management Software Review 52

Wrike

DECEMBER 7, 2009

Demos, a British think tank, described this in a 2004 report as a key moment in the arrival of a “Pro-Am” era, a time when professionals and amateurs work side by side: “Astronomy used to be done in ‘big science’ research institutes. When people ask me about the primary area of Project Management 2.0

Retail 28

Retail 2004 Construction Risk Management 28