Profile picture for user vanderhaeghen

As a new feature, ARIS Business Strategy offers SWOT to support strategy planning and to understand the Strenghts, Weaknesses, Opportunities and Threats organizations are facing when they try to achieve a strategic objective.

Here is a good article about SWOT and how to perform a basic analysis using SWOT: http://goo.gl/xqlK9. Just stop by to learn more.

Even if SWOT comes from a more strategic viewpoint, I guess that there are many other fields of application. So, what do you think of it? Could SWOT bring added value to your daily work even if it is not strategic?

by Sumit Bhandari
Posted on Fri, 08/26/2011 - 10:59

Hello Dominik,

My two cents worth:

SWOT is very useful in not only the Business strategy but also in the requirement analysis, for example, when discussing or reviewing the business process workflow design (when applying business rules to purchase order creation process?).

I also recommend MoSCoW analysis in conjunction with SWOT to give a clearer picture of what needs to be done and in what priority. This is more relevant for Business Strategy than anything else. After all the Business Strategy design involves the Enterprise Analysis process.

 

Regards,

Sumit

0
by Dominik Vanderhaeghen Author
Posted on Fri, 08/26/2011 - 12:37

Hi Sumit,

thanks for your comment! I totally agree that SWOT is also helpful in requirements analysis. I think that you can bring it down to this easy formula: Everytime you want to achieve a certain objective (e.g. gather requirements, find improvement approaches, plan changes etc.) it makes sense to perform a SWOT analysis to get a full view on what to consider during future work.

I haven't heard about MoSCoW yet, but this sounds quite interesting. Would you give us an introduction to this approach? I would very much appreciate if you write a short article in the Business Strategy group which gives us an overview of the approach and its benefits.

Kind regards

Dominik

0
by Jochen König
Posted on Fri, 08/26/2011 - 13:41

The MoSCoW method basically proposes the categories a development project should use to keep a full view on all cusomer requirements and prioritise them for implementation. Tha acronym stands for "Must, Should, Could, Would". From a stategy and self-positioning perspective it is comparable to the Kano diagram emploed in Lean Six Sigma projects.

0

Featured achievement

Genius
You like to help others solve their problems by answering questions.
Recent Unlocks
  • KF
  • KH
  • RG
  • Profile picture for user Vee_ARIS
  • Profile picture for user smarty
  • PacMan

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock