Sometimes I have a brainstorm session with friends/coworkers and it sticks with me. When that is the case I will sometimes start writing a post that grows on me as it progresses. These Brainstorm sessions I have with myself mostly will gather information from other sources around the web, and might contain best practices. But I don’t want to categorize the posts as best practices because I’m not sure about what the actual best practice is. Good examples of a Brainstorm posts are called The deal with Project Failure and What are workdays in Microsoft Project.
There is also a special kind of brainstorming I do, these are the About posts. Big, content rich articles about specific items or subjects related to Microsoft Project or Project Management.
But there’s sure to come more brainstorms in the future. I hope you like the content that’s already here. And if you are interested in doing a brainstorming session with me please let me know in one of the comments.
Hello reader! Welcome to The Project Corner, or how I have started calling it in more recent articles and video’s: TPC.
What originally started out as a blog related to Microsoft Project and Project Server grew into a place for me to discuss anything related to Microsoft Project and Portfolio Management. This includes much more than just those two applications and even extends beyond this WordPress blog that you are now on.
One of my readers requested a place to find all the best content related to TPC. And this article is my attempt to provide such a place.
Project for the web is a Microsoft cloud-based solution that gets new features regularly, as you might know from my YouTube series on the topic. This blog series is about the Feedback portal that we can use to let Microsoft know which new features to include in the product.
This is the second update since the introduction post. I will briefly look at the progress on previously mentioned feature requests and I will take a look at two additional features that might be interesting for Project for the web.
Project for the web is a Microsoft cloud-based solution that gets new features regularly, as you might know from my YouTube serries on the topic. This blog series is about the Feedback portal that we can use to let Microsoft know which new features to include in the product.
This is the first update since the introduction post. I will briefly look at the progress on previously mentioned feature requests and I will take a look at two additional features that might be interesting for Project for the web.
Microsoft used to work with Uservoice to capture the needs and wishes of the community. I covered several Uservoice items in the blog. But in 2021 Microsoft switched to an internal Feedback portal for Project for the web. With the announcement, we are treated to a new way of providing feedback to the Product group at Redmond.
I know I mentioned in blog posts and newsletters that I would be moving more towards the Power Platform . So, it might come as a surprise to see a post (after so long) about Project Management on the blog.
But actually, it’s still very close to my goal of more Power Platform AND my goal to keep writing about project and project management.
Let’s start with a little disclaimer, the following article is a brainstorm experiment by my hand. There’s no real crystal ball involved. This article is an exploration on where the world of Project and Portfolio management is heading.
Obviously, any prediction of the future will change that future because we are preparing differently for it. This was excellently described in the first chapters of Homo Deus a book I’m currently reading (and yes the inspiration for writing this article).
But, because it won’t happen exactly like I describe it doesn’t mean at all that we should not dream about the future. Or write these kinds of articles. There might even be a smart Microsoft employee that reads the article and picks it up and makes it reality.
Just a warning: I couldn’t find/use a lot of pictures for this article. Just chew through the text please :-).
Hi Readers, Here’s another guest post for you to enjoy. It’s the third time for Ashley to join TPC. You might have seen her previous work on the top 5 trends of 2018 and 2019 for Project Management.
This time I’ve asked Ashley to look into Scaled Agile, as I believe it’s a great way to work with Agile and have a structure in place at the same time. So without taking to much time from you, here is Ashley again with
It’s a wonderful world where the TPC blog attracts enough attention that other people want to contribute to it’s content! I’ve had multiple guest bloggers on, some even multiple times such as former colleague Hester Blok (who did an excellent at making workflows in Project Server a lot more understandable).
Today there’s another return author, Ashley Lipman. She contributed previously about the Project Management trends shaping 2018. And is back here with the Top 5 Project Management Trends reshaping 2019.
As with the previous article, I’ll come back on at the end giving you my (Microsoft minded) take on what she wrote. With that, here’s Ashley:
Have you ever worked on a schedule and got the idea that Microsoft just loves to put blue calendar icon’s in front of every task you create? What’s up with that? Well, you created “soft constraints” on every task by manually entering a start or finish date.