Daniel Linman | Your Guide to Project Management Best Practices - Part 12
Daniel Linman

Daniel Linman

IT Software Consultant · Canada
MyMG Contributing Expert since 2010IT procurement & software selection

Daniel Linman is an IT software consultant based in Canada. He works with companies on the unglamorous side of technology: choosing software, negotiating with vendors, and making sure a new tool fits the systems and data rules already in place.

Much of his work happens around SaaS and custom software purchases. He sets up renewal calendars so contracts don't auto-renew by accident, pushes for Canadian-dollar pricing when budgets are in CAD, and asks US vendors about Quebec's Law 25 before any personal data leaves the province. Outside work, Daniel plays guitar and spends his weekends hiking with his family.

All Articles by Daniel

Avoid Inadequate Planning, the Primary Project Management Mistake

Inadequate planning is considered the number one mistake in project management. Many troubles can be prevented and tracked by effective and efficient planning. So this time I’m going to describe what primary mistake some executives make when trying to set up and handle their project initiatives.

The Role of Business Analysis in Project Management

The Role of Business Analyst in Project Management

As a rule, the process of researching and analyzing the activities of a project for possible gaps in business requirements and inefficiencies in solution delivery is carried out by a professional (or an expert group) appointed to the role of business analyst. This professional contributes to solving the solution design and implementation issues in project management by providing expert advice, guidance and leadership to the project manager, team and other stakeholders. The business analyst takes ultimate responsibility for identify and solving problems affecting the business solution, and works closely with the project manager to analyze the existing business systems and make recommendations for improvement.

managing requirements in agile project

5 Best Practices for Managing Requirements in Agile Projects

Success of agile project management greatly depends on the approach to requirements specification which includes several best practices. The agile approach promotes a highly iterative, collaborative environment in which the team, project manager and senior stakeholders enjoy flexibility in addressing any inherent risks associated with managing requirements. An interesting feature of this approach is that a change to project requirements can be turned into a competitive advantage later on, as compared to the traditional approach which doesn’t ensure adaptability to the changing environment. In this article, I write about 5 best practices for managing requirements in agile projects.

project delivery tips

4 Essential Tips on Project Delivery

Do you feel that your project cannot be delivered because it is out of schedule, unaligned with the business objectives or too complex and vaguely planned? Do you have to report to board members about failed delivery? Or perhaps there is lack of finance and team competence? … These and other challenges can break your project. Here’re 4 essential tips that can help you avoid failure and deliver your project successfully.

5 characteristics of a good project manager

Top 5 Characteristics of a Good Project Manager

I’ve been working as a project manager for years, and today I can say for sure that in my profession there is a lot of discussion about what characteristics make a project manager good at PM (project management). Some people think that strategic thinking along with leadership is the greatest characteristic. Others point out analysis and communication as the major characteristics, and so on