Monthly Archives: November 2014

10 Reasons Why Software Project Estimates Fail

Written – July 30 2010
This is a good read..
Here the list
1. The project is poorly scoped
How can you estimate time on a project when you don’t know what that project is? It’s rare to find a client who appreciates exactly how their system should work.
Almost every large project I’ve undertaken has requested “flexibility”. In other words, the client wants the system to handle anything they want at any future point in time — even though they have no idea what those features might be. Flexibility is not a requirement!
2. Development time is estimated by non-programmers
If you’re not a programmer, don’t guess at development times. A project is doomed the moment a manager writes their own fictional estimate. At best, they’ll be completely incorrect. At worst, the programmers will be tempted to prove them wrong.
3. Developer estimates are too optimistic
Developers think in terms of coding hours. Time passes quickly when you’re in the zone and it’s difficult to assess your own speed. Appreciating the speed of other developers is impossible.
Many developers are over-optimistic. They tend to forget the softer side of the development process, such as project management, collating requirements, discussions with colleagues, absences, PC problems, etc.
4. The project is not adequately dissected
Be wary if the development estimate for an individual feature exceeds a week. That chunk should be sub-divided further so the developer can analyze a complex problem in more detail.
5. Estimated time is used
Give a programmer 5 days to complete a task and it’ll take 5 days. Software development is infinitely variable and any code can be improved. If a developer takes 3 days to finish the task, they’ll spend the remaining time tweaking it or doing other activities.
Unfortunately, this results in a situation where estimates become the minimum number of development days. The actual delivery time can only get worse.
6. More developers != quicker development
A 100-day project will not be completed in 1 day by 100 developers. More people results in an exponential increase in complexity. See Why Larger Teams Do Not Result in Faster Development…
7. The project scope changes
This is perhaps the most irritating problem for a developer. A feature is changed or added because customer X has requested it or the CEO thinks it’s a cool thing to do.
Is the impact of that new feature documented?…
8. Estimates are fixed
Estimates should be continually assessed and updated as the system development progresses. Programmers often believe they can make up lost time — it rarely happens.
9. Testing time is forgotten
It’s impossible for a developer to adequately test their own code. They know how it should work, so they consciously or sub-consciously test in a specific way. In general, you can expect to spend another 50% of the development time on testing and debugging.
10. Estimates are taken too literally
Non-programmers rarely appreciate the complexity of software development yet few businesses plan for schedule slippages. The project often sits at the bottom of a huge unstable tower of other activities, such as literature printing, marketing, distribution, etc.
Development hold-ups can cause a costly chain reaction of delays. Unfortunately, it becomes easy to blame the programmer at the bottom of the pile. That’s doesn’t bode well for future projects — the programmer will either refuse to provide estimates or inflate them dramatically.

Do you still have Transfer and Delivery delay notification Disabled!!!???

Written – July 26 2010
Do you still have Transfer and Delivery delay notification Disabled!!!???
Do you enjoy waiting hours to find out that there may be a problem delivering your mail?  I am sure your users enjoy it even less then you.
So let’s get this fixed once and for all.
  • Open the Server Configuration Document
  • Router/SMTP, Restrictions and Controls…, Transfer Control
  • Set Transfer and delivery delay to enabled
  • Adjust the notification interval.
Thats it
here the link for more details or check the help
Enjoy JT

How to deal with view Overdose

Written –  July 22 2010
We all have those Databases which have too many views, or views that have too many sorts or categories and we just don’t know how to deal with them or if there even in use.
Well there is a simple solution to do a quick clean up.
Make sure you have a template of the database incase you end up deleting a view you need, so you can put it back easily.
Once your sure you have a backup ;
  • Go into the admin console
  • Find your database
  • Right click and go to Manage Views …

There you will see how big your view indexes are, and what percentage of the Database they represent.

Sort by size and all the ones with 0 sizes may be views that are no longer used and could be cleaned up.  Be careful to make sure they are not used as lookups or by agents or a view that is used every so often.
Now for the big views, check to see if they are really needed, can they be merged so that one of them can be deleted, is there an alternate view exsiting that is smaller.
Or you can try optimizing the view, reduce the sorts, reduce the categories, reduce the columns, adjust the selection, or basicly simplify and clean up the view.
Here is some quick info to see how this can effect your views
View index size versus response times
View size versus refresh time
A good trick I picked up is to create a cutoff date to exclude all old documents from the view.  This helps to speed up the view and reduce the index size too.
@Year(@Modified) < 2008
Enjoy JT

Optimizing Database views

Written – July 21 2010
Recently I had a user complain that when he uses one of our databases he is getting a lot of lag navigating within the view.
Of course when I test it, it’s always super responsive.
A quick look and I was able to remove the usual suspects

• To many Categorized Columns
• over use of sorts
• selection formula
• Reader field… Bingo
Since I had access to all the data the view was performing perfectly, but since this user had very restricted access to the data, he was experiencing tons of lag.  I won’t go into the details of why this is an issue but simply say that the Domino has to go thru the entire list and determine if the user has access or not to a Document and after a certain amount of accessible docs are reached display the info to the user.  And if the user scrolls down repeat the process….

There are a few tricks to help you out with this.

• The classic Embedded view  using Single Category
• Using a Categorized view
• Then there is another trick I use which I do not find is well documented anywhere, creating a hidden column that is sorted by the reader’s field.  I once read a will written document related to this but can no longer find it, so if you know where it is please let me know or forward it to me.  This trick cause all the docs that the user has access to, to be grouped together so Domino has to deal less with the docs the user does not have access to.
• Just yesterday Andre Guirard posted a new technique which I have never seen and will be testing out shortly, he is using the @SetViewInfo formula to limit the selection.  I urge everyone to take a look at this.  (Thanks Andre for sharing this with us)
There are a few other tricks you can use to optimize your views.  I encourage you to take a look at these articles which lists them in detail. 



Easy way to test out Lotus Notes Traveler useing Greenhouse

Written – July 19 2010
Hello All
Are you still not sure what exactly Lotus Notes Traveler is, or how it works?
Maybe your company is still trying to figure out which mobile solution to use.  Well take five min and give traveler a quick try.
The simplest way to do it is to get your son or daughter’s ITouch, if you don’t have one.
Of course you could use an Iphone, Nokia S60, or a Windows Mobile.
Once you’re all set head to and follow the install instructions.
Play around do some quick tests it is linked to your greenhouse mail account.  During testing I set up a mail box rule to forward some of my mail to my Greenhouse account so I could play around with it a little more.
I know this is nothing new, but I thought I would just remind you all about it

Why can’t we all be like this?

Why can’t we all be like this?
Read this comic today thought it was too kool.
If you Hover over the comic you get the following details.
“Mr. Rogers projected an air of genuine, unwavering, almost saintly pure-hearted decency. But when you look deeper, at the person behind the image … that’s exactly what you find there, too. He’s exactly what he appears to be.”

ACL Audit Tool. Take a snapshot of all your ACL settings for all your DBs

Written –  July 13 2010
Here is a quick, easy, fast and simple tool to find out who can do what to your databases.
An Absolute Life saver.
Infact I run this tool every so often and when ever some one asks me a tuff question about security I can answer it in seconds.
The other kool thing is when ever we do a full audit of ACLs this is a huge time saver.
The best part is that this was created by Big Blue ages ago and it’s the best tool I have ever found.
Check it out
It takes 3 easy steps
 1) Select the server and what you want scanned
 2) Select your conditions and display options.
 3) Select the file name and path
Once you run the tool it generates a HTML file with hyperlinks that point to the database you want to see, the results that look like this.
PS (I know it’s not Thursday)