Gunther Verheyen

OCTOBER 25, 2020

After a few years of searching and experimenting, “Scrum” was documented and presented to the general public. December 2011. October 1995. October 2020. Scrum turns 25. Hip hip hooray! September 2003. I don’t care about titles, positions, certifications, career.

SCRUM 105

SCRUM 2004 2003 2011 105

MPUG

NOVEMBER 23, 2020

Regardless, they should at least be documented as part of a project’s lessons learned so they can add value to future projects. These numbers were about the same in 2011. Boost positive risk-taking: Having a risk-supportive environment that rewards risk and does not penalize failure can allow the imagined to become reality.

Underperforming Technical Team 104

Underperforming Technical Team Technical Review 2011 2015 104

Rebel’s Guide to PM

APRIL 27, 2016

You can upload documents to tasks from the schedule, and add documents to the main project itself from the homepage. This means you can store your Project Charter at a higher level to task-related documents like requirements specifications. A proper Gantt chart). You can also add dependencies and milestones.

Software Review 150

Software Review 2016 Software 2013 150

The IIL Blog

JULY 24, 2018

champions Ken Jennings and Brad Rutter on the game show back in 2011. Here’s what Woodside did (as described in IBM’s website ): Watson was trained – Watson absorbed over 600,000 pages of documents, from reports to correspondence. LeRoy Ward, PMP, PgMP, PfMP, CSM, CSPO | Executive Vice President – Enterprise Solutions, IIL .

Process 103

Process Artificial Inteligence 2011 Energy 103

Proofhub

JULY 29, 2021

Every new employee who joins the company, gets this document which lists all the core principles?—?the Since 2011, their annual Hack Week allows employees to change scenery and go out of their usual workspaces to help them explore and think bigger. Read Hootsuite’s manifesto that cultivates the social revolution inside the company.

2021 159

2021 2008 2011 Innovation 159

nTask

MAY 10, 2021

Her most popular book ‘ Life-Changing Magic of Tidying Up ’ published in 2011 gave rise to a cultural phenomenon, inspiring people to get rid of the excess and focus on the essentials. To stay on top of your A-game, organize your files into different categories and place documents in the order of priority.

2011 148

2011 2021 2019 Consulting 148

MPUG

SEPTEMBER 28, 2020

Since there is an emphasis on documentation, knowledge is not lost for replacement team members and potentially becomes useful for future projects. The Agile model is lightweight, uses an informal communication style, is less document oriented, and uses less defined rules and policies.

Retail 119

Retail PMI 2001 2011 119

Binfire

APRIL 23, 2020

Binfire , after all, has been a remote working environment since we started in 2011. Documentation is a must. Remote teams need documentation more than co-located ones. By documenting all meetings and every decision the team makes, you make sure all information is available to everyone when they need it.

2020 78

2020 Underperforming Technical Team 2011 Retail 78

Herding Cats

MARCH 17, 2019

Establishing the Performance Measurement Baseline (PMB) , AACE Workshop, Denver, Colorado, April 16, 2011. Establishing the Performance Measurement Baseline , AACE Workshop , April 16, 2011. Earned Value + Agile = Success , National Defense Industry Association (NDIA) Conference, 4-6 April 2011, Baltimore, MD. Risk Management.

2003 54

2003 2011 2008 Performance Measurement 54

Rebel’s Guide to PM

MARCH 21, 2022

Good communication is not just about talking and listening to the team – it is also about documenting effectively, producing clear reports and passing those on to the interested parties. This article first appeared in 2011. Read next: Project communication management explained. Making the complex simple.

2007 55

2007 2011 Underperforming Technical Team Innovation 55

MPUG

DECEMBER 31, 2020

I was recently reading the latest posts in the Project Standard and Professional user forum, when I found a recent reply to a question that was originally posted in March 2011. This question and several follow up questions were all answered successfully back in 2011. Background.

2011 105

2011 2002 2019 2010 105

International Institute for Learning

APRIL 19, 2023

DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. They are comprehensive—with hundreds of pages of detailed documentation—to support teams addressing complex problems. They emerged about a decade after the Agile Manifesto. This is a nuanced yet critical distinction.

Agile 59

Agile Cadence Certification Lean 59

Leading Answers

APRIL 22, 2018

“ Software is eating the world ” claimed venture capitalist, Marc Andreessen in his 2011, New York Times article. Also, using a software product provides better feedback on its suitability and possible expansion than reviewing a document or diagram about it.

Technical Review 124

Technical Review 2011 Transportation Development Team Review 124

nTask

DECEMBER 31, 2020

Document & file attachment. The application was launched in 2011 and is a sweetheart of Kanban lovers all across the organizational paradigm. Let’s take a look at the key features, the pros, and cons and what is the price model of the software. Key Features. Add tasks from emails. Analyze & improve your workflow. Copy boards.

Software Review 148

Software Review 2011 Risk Management Risk 148

Scrum.org

MAY 29, 2020

The reason in 2011, Gojko Adzi introduce a different name to group these practices - “ Specification by Example ". And the primary output being “living documentation” and collaboration and with automated tests being specified as the secondary output. TDD is about design and building the product right. Hope this helps.

Software Review 129

Software Review Technical Review 2004 2003 129

Redbooth

APRIL 19, 2017

Back to Google, and we find a slide presentation from 2011 that describes iWorker 1.0, Anyway, according to Ricoh businesses can “activate” iWorkers by using collaboration tools, optimizing business processes, moving to the cloud, and digitizing hard-copy documents. And eWorkers too for that matter. and iWorker 1.5.

2011 70

2011 2012 Defining Software 70

Herding Cats

OCTOBER 24, 2018

Root Cause Analysis is a systematic documented approach to arrive at the true Root Cause of the process problem. The Analyzing Method of Root Causes for Software Problems,” Tomomi Kataoka, Ken Furuto and Tatsuji Matsumoto, SEI Technical Review, Number 73, October 2011. “A Perry, and Dieter Stoll, ICSE 2000. Lehtinen and Mika V.

2014 45

2014 Aerospace 2011 2013 45

ProjectManager.com

AUGUST 29, 2023

Business Plan A formal document that clearly defines the business goals of a project and how to attain them. Communications log A record of continuous documentation of communications between project stakeholders managed by the project manager. It is also called a Business Case. It includes the plans to fulfill these goals.

Software Review 392

Software Review Underperforming Technical Team Lean Event Chain 392

MPUG

MARCH 28, 2021

The legal department gets involved only to work on contracts or to review documents for legal issues. Some audiences review planning documents in detail and approve them, whereas other groups use them simply as direction for the work they perform. Other supporting groups include operations, manufacturing, IT, and other departments.

Planning 90

Planning Underperforming Technical Team Software Review Executing 90

Wrike

SEPTEMBER 29, 2022

Asana was launched in 2011 by co-founders Dustin Moskovitz and Justin Rosenstein. Available with the Business, Enterprise, and Wrike for Marketers plans, Wrike’s proofing software allows managers and team members to add comments directly to documents, images, videos, and Microsoft Office files attached to tasks, projects, and folders.

2006 36

2006 2011 Software Budget 36

Herding Cats

OCTOBER 21, 2018

It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem. Kinscher, a white paper in the "Lean Product Development for Practitioners" series at MIT, 2011.

2011 33

2011 2013 2015 Engineering 33

Leading Answers

APRIL 22, 2018

“ Software is eating the world ” claimed venture capitalist, Marc Andreessen in his 2011, New York Times article. Also, using a software product provides better feedback on its suitability and possible expansion than reviewing a document or diagram about it.

Technical Review 60

Technical Review 2011 Transportation Development Team Review 60

Proofhub

APRIL 17, 2018

ProofHub was launched in 2011 as a solution to provide simple but effective project management. With our file sharing system, you will no longer have to worry about scattered files and documents all over the place. How ProofHub came into being? Simply upload them in ProofHub, share them with people, and easily access them.

2011 60

2011 Software Review Defining Software 60

The Lazy Project Manager

MAY 5, 2016

So for Peter ‘The Lazy Project Manager’ Taylor to be selected as previously covered (Amsterdam 2009, Milan 2010, Washington 2010, Dallas 2011) means 1 x 3 x 3 x 3 x 3 which gives us an 81 to 1 probability, I am quite liking those odds, put me down for ten pounds, it is a reasonable gamble.

PMI 150

PMI 2010 2015 2009 150

nTask

DECEMBER 29, 2020

The first was 2011 when $126 billion in insured losses were reported. Secondly, lack of a well-documented BCP and training on how to follow it can lead to mistakes being made in the stressful situation of a disaster strike. 2012 was previously the third costliest year on record with $77 billion in insured losses claimed worldwide.

Planning 78

Planning Agile 2021 2012 78

nTask

DECEMBER 29, 2020

The first was 2011 when $126 billion in insured losses were reported. Secondly, lack of a well-documented BCP and training on how to follow it can lead to mistakes being made in the stressful situation of a disaster strike. 2012 was previously the third costliest year on record with $77 billion in insured losses claimed worldwide.

Planning 78

Planning Agile 2012 Technical Review 78

Strategy Execution | PMO Perspectives

NOVEMBER 14, 2019

Day One enables you to do whatever journaling you want – and also captures your other social media posts; add photos and documents – and write freehand. Rebecca Grossman and Eduardo Salas, (2011) “The transfer of training: what really matters” International Journal of Training and Development 15:2.

2011 69

2011 PMI PMO Certification 69

Online PM Courses

JULY 2, 2018

Their document are carefully thought-through, well-produced, and always have interesting insights. Alongside their main reports, PMI also produces a slew of in-depth complementary reports and other interesting documents. That’s Figure 6, which tracks five project performance metrics annually, from 2011 to 2018.

2018 65

2018 Technical Review PMI 2017 65

Epicflow Blog

MAY 14, 2019

I saw many lists of thousands of improperly documented LL which are not manageable and thus not useful because of the quality and level of details of the information provided.”. Merrow (Wiley, 2011), recommended by Giorgio Locatelli , an Associate Professor of Infrastructure Procurement and Management at the University of Leeds.

Underperforming Technical Team 75

Underperforming Technical Team Technical Review 2002 Software Review 75

ProjectManager.com

MARCH 4, 2022

The agile values come from the agile manifesto , a document with the guiding principles of the agile methodology. Working software over comprehensive documentation: Before the agile manifesto, software developers focused heavily on documentation. The term scrum values actually refer to agile values applied to a scrum framework.

SCRUM 335

SCRUM Software Review Development Team Review Underperforming Technical Team 335

Workzone

MAY 1, 2020

Pros: Similar to Proofhub, inMotionNow’s biggest asset is for teams handling a lot of creative project documents. Proofhub is a project planning software tool launched in 2011. Pros: Proofhub has advanced markup and proofing capabilities, making it a great option for teams that create a lot of design or project documents.

2020 29

2020 2002 Software Review Technical Review 29

TrustRadius Project Management

MAY 1, 2020

A standout capability of Whereby is its integration with G-Suite, so that users can collaborate on documents from within the Whereby platform. In 2011, Skype made up 40% of all VoIP usage. Whereby is optimized for mid-sized teams who work mostly or entirely remotely. Why Skype Lost The Video Conferencing Battle.

Software Review 116

Software Review Technical Review Underperforming Technical Team Technical Support 116

Planio

JULY 9, 2020

While task management app Wunderlist was released in 2011 and, after being acquired by Microsoft, was discontinued in May 2020. In the App section, keep it to the key apps: Issue tracking, Documents, Forums, Blog, and Wiki. Need convincing? Redmine was launched in 2006 and is still being regularly updated.

2006 88

2006 2007 Closing Agile 88

Scrum.org

OCTOBER 9, 2023

They looked up the date: July 21, 2011. The first document, the PR/FAQ, was authored by the Product Director and a tight-knit group of product managers. The document served to describe a near term Product Goal : an upcoming beta release. Of course, they were aware and they were confused about the relevance of my question.

Transportation 163

Transportation 2011 SCRUM Initiating 163

MPUG

MARCH 18, 2021

To have the process, to have the documentation, a fix to that process, is a wonderful thing. We’ve got to put these headers and footers on all of our documents because of say, like a data governance policy or something like that. Is this applied correctly to that set document? Secondly, right?

Risk Management 52

Risk Management Software Review Underperforming Technical Team Governance 52

Rebel’s Guide to PM

APRIL 26, 2017

Establishing a single source of truth with all relevant project documents, processes, and tasks will make it even easier for the team to deliver as expected. When meeting with stakeholders, review all documents and processes; re-confirm scope and timelines; agree on reporting formats, and clarify any other issues.

Underperforming Technical Team 218

Underperforming Technical Team Software Review 2011 Risk Management 218

International Institute for Learning

NOVEMBER 9, 2022

Many of the skills honed and developed by the business analyst are applicable to being a good product owner: gathering information, analyzing the information, documenting the information, discovering and defining business problems, coming up with creative solutions, and so forth. There are no business requirement documents in Scrum.

SCRUM 78

SCRUM Software Developers Software Development 2011 78