2001 Lean Technical Review 
ProjectManager.com
NOVEMBER 22, 2021
That’s because what we think of as agile really appeared in 2001 with the publication of the “Manifesto for Agile Software Development,” authored by 17 software developers. The term scrum was introduced in a “Harvard Business Review” article from 1986 by Hirotaka Takeuchi and Ikujiro Nonaka. Kanban Methodology.
ProjectManager.com
MARCH 12, 2019
That’s largely due to agile’s ability to adapt to change and incorporate customer feedback, both of which are essential in today’s world where technology is constantly evolving, and swathes of information are just a few clicks away—including public customer reviews. The Principles are Constant.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ProjectManager.com
JANUARY 12, 2022
Technical Project Management Conference. Project management at its core is a technical discipline, and the Technical Project Management conference, produced by the American Management Association, is a great place for those in the IT and technology space. Where: AMA Conference Center, Atlanta, Ga., Website: [link].
Leading Agile
NOVEMBER 13, 2024
I guess it was signed in what, 2001 or no? Yeah, 2001. You have daily standups, you have reviews and retrospectives, you have sprint planning meetings and such. They have a product owner, they’re doing sprint planning, they’re doing daily standups, they’re doing reviews and retrospectives.
Project Bliss
MAY 10, 2017
It came about during a ski trip in 2001. Continuous attention to technical excellence and good design enhances agility. Today both technology and the marketplace can change quickly. Lean software development was originally developed by Mary and Tom Poppendieck, in their book Lean Software Development: An Agile Toolkit.
Scrum.org
JANUARY 27, 2021
Reviewer(s): Russell Miller PST. However the technology of the time was unable to automate at that scale, so the only available “machines” were people. This was the birth of the Agile movement with the Scrum Framework (1993), the Agile Manifesto (2001), and later Kanban (2004). Agile Manifesto, 2001.
Leading Agile
APRIL 24, 2019
Tech Infrastructure != Many organizations divide their technology stack between front-end and back-end systems and place an API boundary between the two. I’m including all IT resources “in front of” the API layer in the organization’s technical infrastructure. Value Stream. Half-Agile Transformations.
Expert insights. Personalized for you.
505 
Let's personalize your content