The power of Context

Written by Danie van den Berg
When inside a maze, it is very confusing (and frustrating) to know where you are, where you’ve been and where the heck you are headed... When however you have the option to rise to a level above the maze and get a higher level view...a better perspective, you gain the ability to find solutions to your predicament more easily.,

That is the power of perspective, of placing your circumstances in the proper context.

This is also true of business problems. It also applies specifically to documenting or modelling complex business process problems, requirements and solutions.

Let me explain what I mean by this...

Often one sits in a meeting room, surrounded by a variety of stakeholders, engaged on a certain set of business requirements. When these stakeholders are from different areas of a business, they typically have their own agendas and reasons for being in that room at that point in time.

Read full article: Click here

Why Agile Isn’t Enough

Written by Richard Larson
(Watermark Learning)

Let me ask you a dumb question: Does your organization produce or provide products or services that customers use? Of course.
But maybe a better question would be: how many of you would like to produce them faster or with more innovation?

If you produce new products or services, you potentially could use a Lean Startup approach and create them faster and with more value. It doesn’t matter if you work for a small company, at a major multi-national company like GE (who uses lean startups), or for government or a non-profit. Lean startups are useful and needed in all industries and organizations.

The Lean Startup method was created by Eric Ries and described in his groundbreaking book The Lean Startup back in 2011. I first came across his work a few years after that and it struck me as intuitively sensible. Part of the reason it resonated with me was a few years earlier our company conducted a lean startup type of effort. We built our Online Study Exams product based on customer needs and Ries’ concepts really hit home. They also made we wish I had known then what I know now. So here is a series of 3 articles to help others based on lots of mistakes and learning! It takes the concepts of the Lean Startup process and shows how business analysis techniques support this process.

Read the full article: Click here

Project Closure - Ignore It At Your Own Risk

Written by Anju Aggarwal
1) the Client gets value from the service they paid for, 2) the Project Manager gets acknowledged for the hard work they put in for the project and, 3) the Project Sponsor (Organization) gets the payment from the client on time. But all these listed completion criteria seldom get completed on time and still the project will be marked as closed. Do you also see the similar situation? Is this a correct way to complete a project? Should we rectify this behavior or not?

Let us reflect on all these questions in this article. We will look at the perspective of our three main stakeholders: Client, Project Manager, Project Sponsor. Let’s also try to understand the importance and impact of the project closure phase in order to justify the significance of this “last” but not the “least” project phase in the project lifecycle.

The primary objective of the project closure phase is to ensure that all loose ends are tied up and that the project manager’s work is approved. Project Closing is the combination of the following when applied to a project:1) Assurance that all the work has been completed, 2) Assurance that all agreed upon project management processes have been executed, and 3) Formal recognition of the completion of a project—everyone agrees that it is completed.

Read full article: Click here