Minimalist, Minimum Viable Product (MVP), Minimalism, Light Weight Travel? What is the common thread among all these? Well, the topic of minimalism has been there on my mind for long, so has been the related work topic, MVP. Let's delve into seeing how we can apply the concepts from minimalism into MVP.
Minimalism is a lifestyle and a trending term for several years now. Minimalism has many definitions for different people. So what is minimalism?

 Here are six more practices that, again, virtually every project will find valuable. These are adapted from our book, Software Requirements Essentials: Core Practices for Successful Business Analysis.

Do you have to do them? Of course not—that’s your choice. The requirements police won’t hunt you down if you don’t. But if you know of any projects that won’t find at least five of them valuable, please let us know. We’ll notify the Guinness World Records people.

BABoK v3 techniques are a lot. There are not just 10, 20, or 30 techniques but 50 techniques, to be precise and that's not a small number!

The human mind can remember 5 to 7 elements at a time and anything more than that is hard to remember.

Then, how can one remember 50 techniques?

"Is it really possible to have a BABoK Techniques Mindmap?"

Many of you may wonder.

So, here's the Ultimate BABoK techniques mindmap which could save you 40 hours of your International Institute of Business Analysis (IIBA) exam preparation!

An information system maintains data in fields within records. Equally important is the system’s ability to navigate between records. Parts 5 thru 9 of this series discussed fundamental business data field types. This article discusses a record navigation field. These fields do not themselves contain business data, but support the system’s ability to navigate from a given record instance to business data in related record instances.

Informed business analysts know that one of the secrets to producing a high-quality process model is to establish a clear mission for each model. To be successful, you should mindfully establish the mission of your next process model within the business process management, information technology, or regulatory compliance project that the model will serve.  You will then tailor your elicitations of the model’s content and configuration to meet project needs. Part of your process model mission-setting elicitation agenda will include asking and answering this important question: What is this model’s required degree of abstraction?