Or Redwiki! It is the recently announced Best Practices in Domino Application Development. I am especially excited about this since I have been preaching best practices for many many years.
There are 5 other people that will be on the team. I do not know their names yet, but I am looking forward to working with them.
We start a week from Monday and continue for 5 weeks or so. So I will be very busy until we have completed the task..
If you are on the same team leave a comment and let me know.
Showing posts with label Best Practices. Show all posts
Showing posts with label Best Practices. Show all posts
Thursday, July 28, 2011
Tuesday, October 27, 2009
Major, Minor, Point, HUH?
Application versioning, Code and element level versioning, both make sense.
If you are covered by any regulatory compliance than it is more than a good idea. If not it still makes sense to use versioning to control releases into production.
What is a good version numbering scheme you ask? The most widely accepted model is the Major, Minor, Point. (8.5.1 for example)
Major Releases deliver new functionality and may include new products. Major releases also contain bug fixes reported on a previous major or minor release.
Minor Releases deliver bug fixes reported on a previous major or minor release and may also include new functionality.
Point Releases deliver bug fixes and minor enhancements.
So lets use Lotus Notes for an example. (This is all in fun)
We have Release 8.5. IBM releases 8.5.1. this scheme would have me believe that there are no new features, just bug fixes and some minor enhancements! Hmmm I guess having Domino designer in eclipse is only a minor enhancement :-) I personally would have called it Release 9 (Again based on this scheme).
Some people have Design element level versioning as well. This means you need to effectively comment your code to include the version number. This will simplify testing and auditing changes.
Element versioning is typically overkill for most Notes shops, but I worked for a FDA regulated company, and we had to do this, (I was not so bad).
So to recap:
Application versioning is good, provides many benefits
Design element versioning is good also but may be more work than is needed for some environments.
Happy coding
If you are covered by any regulatory compliance than it is more than a good idea. If not it still makes sense to use versioning to control releases into production.
What is a good version numbering scheme you ask? The most widely accepted model is the Major, Minor, Point. (8.5.1 for example)
Major Releases deliver new functionality and may include new products. Major releases also contain bug fixes reported on a previous major or minor release.
Minor Releases deliver bug fixes reported on a previous major or minor release and may also include new functionality.
Point Releases deliver bug fixes and minor enhancements.
So lets use Lotus Notes for an example. (This is all in fun)
We have Release 8.5. IBM releases 8.5.1. this scheme would have me believe that there are no new features, just bug fixes and some minor enhancements! Hmmm I guess having Domino designer in eclipse is only a minor enhancement :-) I personally would have called it Release 9 (Again based on this scheme).
Some people have Design element level versioning as well. This means you need to effectively comment your code to include the version number. This will simplify testing and auditing changes.
Element versioning is typically overkill for most Notes shops, but I worked for a FDA regulated company, and we had to do this, (I was not so bad).
So to recap:
Application versioning is good, provides many benefits
Design element versioning is good also but may be more work than is needed for some environments.
Happy coding
Thursday, July 9, 2009
Managing Expectations
Everyone has expectations. Your clients (internal or external), your co-workers, your manager, and even family and friends have expectations of you. Managing expectations, in my opinion, is a huge part of our life, especially at work.
We work in a high paced, highly fluid environment; where managing expectations are critical. Change requests to requirements are frequent and not always documented.
According to The Consulting Academy and Brazos Consulting:
Expectations are deeper and broader than "requirements:"
Expectations are your client's vision of a future state or action, usually unstated but which is critical to your success: A client who "wants the project to be quick and dirty," or who "wants to be involved in all the details" or "not involved at all," or who expects that your project will result in "reducing his work force by 80%."
Expectations are set by all kinds of events. Something you said or did, or even the way you said it, something somebody else said or did, or something the client picked up from somewhere else. But it's important to know that expectations, rational or irrational, valid or invalid, are not developed in a vacuum.
So we have requirements; that state what you are creating and how it should work, and expectations; what the client perceives the application can do. In most cases the two are not even close.
Client A requests an application to track employee training. They submit the requirements, ask some questions and off they go knowing what the application you are building does. Over time they see other systems and how they function, may talk to a co-worker to see if the functionality can be added in to their app. Now the co-worker, not having a clue what you are doing says “Sure Notes can do that”. Do you see where I am going?
The Intranet Journal has a very good article titled Managing Project Expectations . Six Keys to Successfully Managing Expectations
1. Know Your Capabilities
2. Set Clearly Defined Expectations
3. Educate and Empathize
4. Be Realistic
5. Continuous Monitoring
6. Communicate Early and Often
A key take away form the article is:
When defining expectations, resort back to the SMART rule of goal setting: Specific, Measurable, Attainable, Realistic, and Time-bound.
Most importantly, make sure all parties are in agreement with what the expectations are from all parties. Again, perception is reality.
So while properly managed expectations should not have an adverse effect on the outcome of your Lotus Notes Development or Administration project
We work in a high paced, highly fluid environment; where managing expectations are critical. Change requests to requirements are frequent and not always documented.
According to The Consulting Academy and Brazos Consulting:
Expectations are deeper and broader than "requirements:"
Expectations are your client's vision of a future state or action, usually unstated but which is critical to your success: A client who "wants the project to be quick and dirty," or who "wants to be involved in all the details" or "not involved at all," or who expects that your project will result in "reducing his work force by 80%."
Expectations are set by all kinds of events. Something you said or did, or even the way you said it, something somebody else said or did, or something the client picked up from somewhere else. But it's important to know that expectations, rational or irrational, valid or invalid, are not developed in a vacuum.
So we have requirements; that state what you are creating and how it should work, and expectations; what the client perceives the application can do. In most cases the two are not even close.
Client A requests an application to track employee training. They submit the requirements, ask some questions and off they go knowing what the application you are building does. Over time they see other systems and how they function, may talk to a co-worker to see if the functionality can be added in to their app. Now the co-worker, not having a clue what you are doing says “Sure Notes can do that”. Do you see where I am going?
The Intranet Journal has a very good article titled Managing Project Expectations . Six Keys to Successfully Managing Expectations
1. Know Your Capabilities
2. Set Clearly Defined Expectations
3. Educate and Empathize
4. Be Realistic
5. Continuous Monitoring
6. Communicate Early and Often
A key take away form the article is:
When defining expectations, resort back to the SMART rule of goal setting: Specific, Measurable, Attainable, Realistic, and Time-bound.
Most importantly, make sure all parties are in agreement with what the expectations are from all parties. Again, perception is reality.
So while properly managed expectations should not have an adverse effect on the outcome of your Lotus Notes Development or Administration project
Wednesday, April 15, 2009
Lotus notes coding standards? Sure have some
It has been my experience that a lot of Domino shops want to enable some sort of coding standards, but they do not know where to start creating them. Also there are not any good examples that I have found available.
Over the years I have come up with a template I use when implementing coding standards in my organization. You can get them here.
This document is a good example of what you can do to create such a document. Use it as you see fit. If you do use it drop me a line and let me know how it worked for you. As always I will answer any questions you may have.
Happy Tax Day my American Friends
John
Over the years I have come up with a template I use when implementing coding standards in my organization. You can get them here.
This document is a good example of what you can do to create such a document. Use it as you see fit. If you do use it drop me a line and let me know how it worked for you. As always I will answer any questions you may have.
Happy Tax Day my American Friends
John
Subscribe to:
Posts (Atom)