Tuesday, May 5, 2015

#businessanalysis for beginners. Internal motivation and struggles of BAs

Have you ever wondered who are these people who do business Analysis and why are they doing it?
I had the fortune to facilitate series of BA workshops where I got to ask questions to real-world BAs.
At the first meetup I have asked what drives them to do analysis?

After all, a good chunk of developers are trying to stay away from it, and since I have came out of that crowd, I am curious why people choose to do BA

So, here is how they have answered what business analysts love and what challenges them in BA
websitewer
Motivation and struggles of BA

I can't deny the truth any longer...#businessanalysis @CoggleIt


Last 10 years I have been working as a software developer/tech/team lead/PM. I have spent seems like an eternity working with different flavors of SharePoint. I liked that too.
So, it's time to move on....
and uncover my passion in BA! I looooove business analysis! 
During years working with SharePoint I was wondering what kept me fascinated by it and I know now - ability to use platform to deliver business value quickly:
Feature tree on coggle.it
  • I don't have to spend months to craft some basic and needed business processes for people who need solution, not technology per se;
  • I got to spend more time talking with people to understand their current challenges and co-create with them solution to solve and less time staring at the code.
Last year I walked away from SharePoint and started leading the custom development project.
I have successfully compensated absence of SharePoint in my life with BA activities on the project.

So year later, I am ready to shift focus in my blog - starting now, posts will be more on business analysis side and not so much or maybe not at all on development.

I am sorry SharePoint developers/administrators, I already lost bunch of you, and will lose even more.

Business analysts, I would love to connect with you and promise to share my BA experience, techniques and tools that make BA effective.

By the way, this first post featured my latest nugget in BA toolset - https://coggle.it/ - an extremely useful and free! tool that helps to do not only mind mapping, but feature tree too.


This tree was a huge success in my project to visualize:

  • scope of the project;
  • priorities using colors, 
  • as well as completion of the features.


Wednesday, February 18, 2015

#APIM Dashboard. Usage report: Blocked, Failed, Other calls

Azure API Management shows the API usage report with the categorization:
Blocked;
Failed;
Other.

Recently my client asks what are the criteria used for these categories.
And here we are:

Successful: 2XX 
Blocked: 403 and 429 
Failed: 5XX 


The rest are counted as other.

Thursday, January 22, 2015

#AzureAPIMgmt '<'quota calls="x" renewal-period="seconds"'>'. Does this allow x call in total per product, or x call per API inside the product?

Azure API Usage Quota Policy allows you define quota per product , per api , per method
   
The question that I have got from the client was the following:

Quota calls on the product level = x. Does this allow x call in total per product, or x call per API inside the product?

Answer: <quota calls="x" renewal-period="seconds"> allows total X amount of calls per product.

Example:

Quota per API
I have a quota setup per API.  Every 60 seconds we can call 5 times each specified APIs. If we exceeds, we get 403 Quota Exceeded
For example:
I call "Echo API" 5 times. Then I am trying to call it one more - 6th time. Failed. 403 Quota Exceeded
But I am still able to call "My Echo API" 5 times after I have called 5 times "Echo API".



Quota per Product
Now, I have modified the policy , I have put calls="5" on the product level. Every hour we can call 5 times any APIs in total per product.

For example: I call "Echo API" 3 times, then I call "My Echo API" 2 times.  Total=5. Then I am trying to call "Echo API" again. Attempt is failed. 403 Quota Exceeded


P.S.

It's worth to note that you can't set less than 3600 sec renewal-period on the Product level in case you set calls limit on the product level.

One of improvements that I want to suggest to MS - is to provide error messages for Policy editor, as well as IntelliSense.

The  only indicator now that is something wrong with the policy is the fact that I can't save it . How do you know you saved the policy? It should be grey out when it's saved.



Friday, May 30, 2014

#SP2013 The server was unable to save the form at this time.

A user can't edit  and save properties of the document.
In my case it turned out to be a permission issue.
The document library uses a document set which in turn uses a custom content type that were defined on the site collection level.
The lib was created under some site (spweb) , the lib has unique permissions
The user doesn't have access to the site, but has access to the lib.
The user can upload and check in  the document to the document set, but can't edit and save the properties of the custom document content type (which is used in the document set).
Every time the user hits the save button he gets the client-side error -
"The server was unable to save the form at this time.Please try again."
I have traced the issue when the user attempted to create a document set item. He got an error: "Access denied".
It happens because SharePoint uses the link ~site/_layouts/15/NewDocSet.aspx that is not accessible by the user since he doesn't have access to the site.
The obvious fix in my case to give access to the site to the user.

Thursday, May 29, 2014

@project SP1 for #Project2013 introduces the old bug with missing resources

‘Lost Resources’ bug has came back after re-relased SP1 for PS2013 has been applied.
To fix it - you need to manually re-add the missing resources in the project.
Plus, you need to run the SQL to fix 2 PS procedures, as it was recommended in http://support.microsoft.com/kb/2933444
draft.MSP_WINPROJ_DELETE_OLD_PROJECT_RESOURCES
pub.MSP_WINPROJ_DELETE_OLD_PROJECT_RESOURCES

I have run the sql before SP1, then I have applied SP1 and compare procedures before and after:
1. [draft].[MSP_WINPROJ_DELETE_OLD_PROJECT_RESOURCES]
The procedure was re-created by SP1 (the service packed was installed on 5/21/2014)
and the SQL delete statement lacks filter by PROJ_UID
 WHERE RES_UID IN (SELECT RES_UID FROM @resUids)

2. [pub].[MSP_WINPROJ_DELETE_OLD_PROJECT_RESOURCES]
The procedure was re-created by SP1  (the service packed was installed on 5/21/2014)
and the SQL delete statement lacks filter by PROJ_UID
 WHERE RES_UID IN (SELECT RES_UID FROM @resUids)