Gunther Verheyen

OCTOBER 25, 2020

After a few years of searching and experimenting, “Scrum” was documented and presented to the general public. October 1995. October 2020. Scrum turns 25. Hip hip hooray! I record a few highlights of “My life of Scrum”, a few aspects from the past 17 years of the life of an independent Scrum Caretaker. September 2003.

SCRUM 105

SCRUM 2004 2003 2011 105

Gunther Verheyen

JANUARY 27, 2021

In May 2004 I attended a CSM class (“Certified ScrumMaster”) by Ken Schwaber in Brussels (Belgium). I was describing, documenting, presenting and trying to sell our approach and offerings of Scrum and Agile transformations. In October 2003 my life of Scrum started, albeit not with Scrum.

SCRUM 103

SCRUM 2012 2010 2011 103

Redbooth

AUGUST 30, 2018

launched in 2004. Shared documents: project documentation, notes and memos, reports and analyses. Team wiki: general company information, onboarding materials, client information, style guides, how-to documents. Managers are more likely to create and update shared documents at first. Source: Tettra.co.

2004 60

2004 Innovation 2018 Executing 60

Redbooth

AUGUST 30, 2018

launched in 2004. Shared documents: project documentation, notes and memos, reports and analyses. Team wiki: general company information, onboarding materials, client information, style guides, how-to documents. Managers are more likely to create and update shared documents at first. Source: Tettra.co.

2004 60

2004 Innovation 2018 Executing 60

Redbooth

AUGUST 30, 2018

launched in 2004. Shared documents: project documentation, notes and memos, reports and analyses. Team wiki: general company information, onboarding materials, client information, style guides, how-to documents. Managers are more likely to create and update shared documents at first. Source: Tettra.co.

2004 60

2004 Innovation 2018 Executing 60

The IIL Blog

APRIL 27, 2018

Shared drive storage for document access. Here are some examples of SMILEs that I began to create in 2004 in conjunction with my dissertation that focused specifically on project management. Webcam equipment for real-time video conversation. Evolution of Learning Exercises for Collaboration.

Software Review 121

Software Review 2004 2012 PMI 121

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). In the complex world of Sales, Marketing, and Software Development, we also needed new ways of thinking that would power the same ideas from Toyota and Lean into the high variance world of complex cognitive work.

2001 207

2001 Software Review Technical Review Underperforming Technical Team 207

Tony Adams

FEBRUARY 24, 2021

McKenzie (2004) studied this question by using a qualitative case study to look at how consultants source, exchange and apply specific knowledge within a medium-sized Australian consulting firm to solve client problems. Personal experience, documents, databases, etc. Organisational knowledge accumulates over time.

2004 40

2004 Construction 2001 Consulting 40

Wrike

AUGUST 31, 2023

A bill of sale is a document that transfers the ownership of a good from one person to another. So, is it worth taking the time to draw up this document? You’ll both want to have that document for your records. Here are the questions your document should clearly answer: What is the selling price of the item?

2004 36

2004 Transportation Technical Review 2023 36

Scrum.org

FEBRUARY 3, 2020

Instead of using the Product Backlog as a form of documentation and knowledge transfer, it is used to facilitate communication and stigmergy within the Scrum Team. 2004) _How can we think the complex?Retrieved The sprints, the Product Backlog and the Sprint Backlog act as aids in the situated cognition of the team. Being there.

2002 191

2002 SCRUM 2007 2003 191

Herding Cats

MAY 7, 2019

61, September 2004. Measuring Software Functionality Using Function Point Method Based on Design Documentation,” Anie Rose Irawati, and Khabib Mustofa, IJSI International Journal of Computer Science Issues, Vol. Dasari, IFPUG 2004 Annual Conference, 23 September 2004. “On 9, Issue 3, No. 1, May 2012. Prakash and V.

Estimate 40

Estimate Software Review Software 2012 40

Herding Cats

NOVEMBER 7, 2016

Group Processes in Software Effort Estimation,” Kjetil Moløkken-østvold and Magne Jørgensen, Empirical Software Engineering, 9, 315–334, 2004. Overconfidence in Judgment Based Software Development Effort Prediction Intervals,” Magne Jørgensen, Karl Halvor Teigen, and Kjetil Moløkken-Østvold, Journal of Systems and Software , February 2004.

Estimate 64

Estimate 2006 2005 2013 64

Herding Cats

MARCH 17, 2019

An Introduction to IMP/IMS , 17 Oct 2004. E lectronic Document Management Tutorial: The Functional Architecture of an EDM System in the Process and Manufacturing Industries. The Five + One Easy Steps to an Integrated Master Plan and Integrated Master Schedule. The Simple Problem of Schedule Performance Indices.

2003 54

2003 2011 2008 Performance Measurement 54

MPUG

MARCH 25, 2021

Number one, we want to define and describe essential documentation and the team ramp-up to SIPOC workshops. So we’ll discuss a lot of the documentation and some of you, maybe all of you will recognize exactly what those documents are. And welcome back to a session two for SIPOC for Workshop Facilitation.

Technical Review 52

Technical Review Underperforming Technical Team Risk Management Software Review 52

Paymo App

SEPTEMBER 8, 2017

Also consider your internal costs: what would you need to invest for onboarding new team members, transferring your existing project documentation and schedules or training the team? Launched in 2004, it’s aimed at giving you a better handle on your business and the work your teams are doing. How can you access support for the product?

Software Review 104

Software Review Technical Review 2017 2016 104

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. Faulty requirements management was a matter of documentation, proper elicitation. If you don’t have that documentation, then you will not be able to know.

Software Review 52

Software Review Technical Review Underperforming Technical Team Risk Management 52

Herding Cats

APRIL 16, 2019

An Introduction to IMP/IMS , in 2003, the Federal Government revised its acquisition policies with a procurement strategy focused on process improvement and acquisition reform implemented by Performance Based Management, 17 Oct 2004. The project management process is well defined, well documented, mature, and available to anyone anywhere.

Technical Review 42

Technical Review Performance Measurement Underperforming Technical Team Governance 42

Knowledgeline

DECEMBER 13, 2004

Knowledgeline Monday, December 13, 2004 Speaking of mergers. Low Documentation Loan (SBALowDoc) SBALowDoc is the SBA’s quick and easy program that provides a guaranty on small business loans of $150,000 or less. Forget 31 flavors, well be confronted with the question of Would you like chocolate or vanilla?

Technical Review 40

Technical Review Software Review Finance Engineering 40