We are pleased to announce our book about MS SharePoint written in simple language! For more details please visit the book website. Thank you!
Wednesday, November 7, 2012
Wednesday, October 3, 2012
Recently I have ensured again that the main challenge for SharePoint professional in an organisation is the business processes setting up. There is no problem to organise corporate information and to build information architecture. There is no problem to provide shared workplaces for the business teams. Even there is no problem to automate existing processes. The problem is to set up correct business process when there is nothing existing.
Lets take some common process of permissions management. IT guys would like to control everything and would like to manage each particular operation with sensitive data. And this approach may be useful, but not for collaboration. In SharePoint all contents is the collaborative asset. So, the main business value of that system is sharing and team work with the documents. The mandatory condition here is a read-write access to document for each team member. The real life systems, unfortunately, rarely meet this simple condition.
Commonly I met situation when all SharePoint permissions managing by IT Service Desk. This does mean that SharePoint system administrator receiving 50 tickets each day with sentences like “I need access to sales report for March of 2011”, “Why I unable to read the corporate financial statement” or “Could you please remove that party photo where I am dancing on a table”. And our system administrator have no idea where this files located. So, he or she have two options: find file and grant the access or ask a team leader whether the person should have the access. In the first scenario it is obvious that corporate security not working – each employee can have the access if asking. In the second scenario the ticket returning back to business representative for approvement.
We have more requests, more bureaucracy, more time, more routine work for IT, less value for the business, less satisfaction with IT department, less satisfaction with SharePoint. And the only reason for that is the total control for IT guys and misunderstanding of the base principles of collaborative environment.
Monday, August 20, 2012
I have just finished Proof-of-Concept for one of our customers. The PoC was a demonstration of capabilities to automate paper document flow based on a custom solution for MS Dynamics CRM 2011. It involves barcodes generation, bulk document printing, scanning of paper documents and automatic recognition of the barcodes and handwritten text within the documents. The solution uses QR Codes to identify the documents.
The most interesting is that we can produce some real documents (see photos inside!) and automate process using standard office equipment like printer and fast speed scanner. That was a big part of work and it have been successfully delivered within three weeks. Lets see how I have done this.
Friday, August 3, 2012
Scenarios of MS Dynamics CRM 2011 Online usage in Windows Azure hosted applications and Silverlight applications with cross domain access
Today we will briefly go through the usage of Microsoft Dynamics CRM 2011 Online data in external applications. The most interesting business case there is the usage of Windows Azure cloud hosting for our application. Windows Azure has some differences comparing to common dedicated server environment. That is why it requires another approaches to applications development and integration.
So, lets say that we have a web site which hosts fast and beautiful Silverlight application. And we would like to show some data within the application. Lets also say that we are a small company who would like to use all benefits of Windows Azure hosting environment.
Thursday, July 26, 2012
Recently I have provided the proof of concept for a customer using CRM 2011 Online and I was surprised how hard it could be to configure the cloud based solution for the typical task of e-mail requests automation.
The task is simple. A company allowing the requests from the customers. Some customers could send formalized request in paper by post. Another group of customers could fill the web form on company’s website. Both requests should be stored in CRM to simplify the relationship management. If you are familiar with the capabilities of Dynamics CRM product than it is obvious that it is enough to use a standard functionality for e-mail processing using queues. So, proposed solution:
Sunday, June 24, 2012
- Basic facts
- Starting point (model AS IS)
- What we are trying to achieve (model TO BE)
- Rules of review
- Atlassian products to implement the solution
- Complete sample
The Source Code Review is an activity which is commonly in a long list of "good to have" things. There is the arguments about lack of time and resources for review. But the aim of the review process is to improve the quality of the source code and to decrease the risks for the project. Is the quality worth of that efforts? Definitely!
Without a code review a development team member may loose the understanding of a high level architecture and produce a bad code which is hard to support, maintain and change in future. In the code review process the new component will be critically considered and evaluated. Two pair of eyes is always better than the one. By the way, in Google company a developer in order to be promoted may spend approximately 20% time on the source code review.
Friday, June 15, 2012
My name is Pavel Korsukov. I am a technical architect, a .NET developer and a person who is interested in how the IT systems work. I have developed applications, managed requirements, directed a team and contacted with system architecture on day-to-day basis. Now I would like to write about projects I participated in.
In this blog I would like to describe the real life systems which I had the honour to plan, develop or support. My aim is to warn my readers about mistakes in the architecture I saw and to enrich them with my real life experience. Also I will describe the internal processes which accompany the technical design of a complex system.
Technical architecture of the IT systems without a dedicated architect rarely follows single strategy. The more releases are made the more unclean an architecture become. New requirements and the lack of time cause a bad architecture. Things are worse if there is no separate person who is responsible for system architecture and the company’s infrastructure integration. I will try to demonstrate how to avoid this by means of organization management, strategy planning and usage of automated tools.
System architecture is suffered from the lack of knowledge. There are a lot of architecture frameworks. But there is a gap in the knowledge about details of implementation. Real life experience doesn’t accumulate within the area. It is true for IT as a whole industry. To help freshmen in adaption with the complex systems is also a task for this blog.
Please hold in mind that depends on requirements the technical design can be substantially different. It major depends on speed, load, resources and development time requirements. So, all information is provided for general information purposes only. You can use it on your own risk.
Text, images and the other content of this blog are protected by the Creative Commons license. Please link this blog if you quote it or if you use some of my materials. Please contact me if you would like to use it for commercial purposes.
I am not a native English speaker. That is why any corrections of grammar are welcome. If you have some interesting projects to discuss you can contact me on LinkedIn.
Your comments are welcome! Let’s start!