Every employer wants to start working in Agile mode to get its various advantages. On they contrary, very few really works on building Agile teams. Not every team is an Agile team. Its very tricky when it comes to delivery 
Some important aspects to keep in mind while building an Agile team are but not limited to:
It is always hard to define how scalable your application is and to plan how we will scale our application. Whenever there is a debate we had plenty of things and yet left with hard situation of how to final.
Scalability as usually defined is the ability to increase the throughput of our application by adding more hardware to our system. In this context there are two options either to Scale up or to Scale out.
Disaster recovery is something every one looks to here is in place. In fact very few companies ever tried to actually review the plan and exercise is as well. In hard economic situations, organizations find it hard to actually implement disaster recovery practices with full strength but they also need it for a good selling point.
While delivering a training session on development life cycle, a discussion started stating we should have separate development life cycle for agile. Let’s discuss should it be really separate? Let’s talk about in term of phases. I will not write down the name of the phase just for the comparison purposes. Let’s look at both models and focus of phases within them:
I have faced a weired issue while upgrading SharePoint Server 2007 to SP1 on one of our development servers. Whenever I executed WSS and MOSS upgrade installer, it gives me error “detection failed, this could be due to corrupted installation”. I tried following to overcome the issue but none of them actually worked:
I have been facing an issue after inserting quite much data for testing into one of my lists. It was really hard to get rid of the data and the deletion in sequence was just a nightmare. After some googling I figured out batch deletion would be a perfect solution. Sample code is shown in the following:
As my data was huge in size like 100,000+ records were there. I prepared batches of thousands and deleted one batch at a time. During each batch, I applied a sleep as well. This way deletion was so fast that I was able to delete all records in like less than an hour.
If you have been reading stuff about sharepoint, you must have read/listened these three terms invariably. Yeah template, theme and site definition. All these three are different, lets talk about each one of these:
Themes
Difficulty level for this entity is lower. This is a collection of stylesheets and images to help creating a skin for the site. It’s all about the look and feel of your site. There are several style sheets already available in “TEMPLATE\LAYOUTS\1033\STYLES” folder. But it is not recommended to modify these directly as it will effect other sites as well. Themes are available under “TEMPLATE\Themes” folder.
I had to pass through a scenario that may rare as far as working with MOSS is concerned, sharing it on my blog so it might help someone else. I had built an office automation application using MOSS. We need to pull legacy data within our application as well. In the application there were several sharepoint views.
Problem
After performing import for the legacy data, the total count of items was like more than 150k. I see the following problem opening up page in designer:
Have you ever wondered what is company loyalty ? Is there something like that or its just for exploitation or something else ? Lets look it other way round. For instance, you are loyal to company and in turn your employer, is your employer in return loyal to you as well ? If you say yes, I doubt it
Having said that, is it required to love your company or your work ? If you just love to work for your company and not your job, you are not fulfilling your duties. Top priority should always be your job and work not the company.
When company will do good business, employer will happily say its your company and when its the other way round, the same employer would say this is my company and I have to take some hard decisions Is n’t it ?
When I joined my first job, I have never thought will I leave this organization or not? As per circumstances I remained for a while with the employer despite of quite much post WTC financial crisis with the company. Anyways, I left when company asked me to
As my career moved onwards, I switched some companies due to many factors like:
everyone seems to be manager and you never know who you are ?
 |
I'm Waseem Arfi running this Blog. Thanks for visiting my Blog. Feel free to send your comments to Me |
Site Visit Count | |
|
|
|
Recent Comments