Tuesday, March 19, 2024

The latest news from the world of project management

How to fail well...

Failure Is the new success. Here are five ways that you can embrace...

5 Skills Needed To...

Why do projects fail? It's a question that invites a lot of interest and...

Embrace the change: Getting...

New IT systems for a growing business can be an exciting prospect and...

Does a Project Manager...

What makes a successful project manager is a combination of their academic abilities,...
HomeGeneralStraight Talk on...

Straight Talk on Project Management VOLUME II – Free E-Book

IT & Project Management
IT & Project Management

With the success of my first eBook, I am delighted to publish Volume II.

The book covers a wealth of topics from Stonseed’s Project Management as a Service and our IT services, to an array Project and Programme Management issues.

Volume II of Straight Talk on Project Management is now available for download as an online Flip Book, PDF. and as a Kindle book.

Click here to get your copy

Related Posts

Continue reading

From ‘a meh thing’ to amazing! How PMaaS can help build innovation into IT Projects

Experience and anecdotal evidence suggest that Bex isn’t alone in seeking a little bit more. In many organisations now, IT project teams feel that the necessary fixed scope, set budgets, tight deadlines, limited resources and defined roles and responsibilities, leave little or no room for experimentation and innovation. The thing is, if you’re getting the results, do you need the added sizzle of innovating? I think that you do.

Every IT project needs a Dale!

This is one of the things I love about Stoneseed, our team, and the culture we have evolved. When we talk about someone behind their back, it’s always positive and hugely complimentary!  If you haven’t yet had the pleasure, Dale Beeton is Stoneseed’s Head of Client Engagement and, as our clients will attest, he is one of those “extra milers” that make a real difference – and not just from a business perspective.

IT Project Management: Nailing know-how, but are we wondering why?

The trainer was explaining the team’s fairly unique binary approach to scrum sprints, which effectively boils down to them having two duration categories – A) one week long and B) three weeks long. The new hire found this interesting and enquired about the reason behind this approach. In her last job, length and number of sprints would be decided at a goal setting meeting, a twelve-week scrum project could have 15–20 Scrum sprints, which could be as short as a handful of days and as long as a month. So, “Why?” seemed a reasonable question but it was met with either blank expressions or an unsatisfactory explanation. The trainer did not know, nobody on the team could answer either.