Just Start on Getting Real… 7

Unity

It is important in an organization and even in a team to have unity. But what some organization does is they split and specializes some of their activities. This environment will result into a communication barrier. Having their own way specializations and teams, they won’t or they are not able to communicate with the others. Having split into different specialization will disable the ability for them to view the project as a whole. They will now think something that is in line with their specialization. The solution to this is for them to integrate those teams and communicate with each other. Let them help each other. This way, more ideas will be used and less time will it consume to finish the project.

Alone Time

Sometimes, people just want to be alone. The same saying goes with employees. People are moody. They can only get productive when they are in the mod to do so. This time is most often the time they are alone. Being alone is the time in which people can get thing done more and quickly. It is the time in which the person is most comfortable working. It might be at morning or night or in the afternoon. Or maybe the person is comfortable working in a place where he or she is alone because no one is able to bother or to disturb her. He or she will have focus. Having a time alone will let the person to throw away unnecessary activities. But of course there is also a need for people to also work together with other people.

Meetings Are Toxic

Companies do meetings when there is something to clear about. It is maybe because the concept is not clear. There shouldn’t be any meetings needed if the concept of a project is clear and concise. A meeting

Really is not necessary. It must be avoided most of the time. This is because a meeting will only cost you time. A meeting will only delay you from getting work done. But if it is really needed it should only be a 30 minute meeting and the person in the meeting is a few important and chosen people only. Most importantly the meeting must have an agenda.

Seek and Celebrate Small Victories

Motivation is important in software development. Motivation lets you finish you work quicker and better. A way to motivate employees is to have something done quickly. Don’t do projects that are too long to finish. Instead of releasing software for months or weeks, release something small in days. The release can a little bug fix or a new feature that is small, or removing some unnecessary fields.

Links

AS1css zen garden – http://ajt2989.site90.com/csszengarden/

AS2 customized zen garden- none

AS3my drag and shop (HW)- http://ajt2989.site90.com/cart/cart.php

AS4fancy box- http://ajt2989.site90.com/fancybox/

AS5lightview- http://ajt2989.site90.com/lightview/lightview.html

AS6AJAX Forms using JQuery-http://ajt2989.site90.com/ajax-jquery-demos/generator/

AS7ajax(quotable quotes)- http://ajt2989.site90.com/Quotes/

AS8ajax contact form- http://ajt2989.site90.com/jquery_ajax_contact_form/

AS9ajax-form- http://ajt2989.site90.com/ajax-form/

Just Start on Getting Real… 6

When developing a software, those who are developing it should be able to think even at the start to finish the software as fast as possible. It is a good way to increase motivation.  You can skip those not so imprtant details as long as it will finish the software faster. With a running software, they will be able to understand more what the important things are.

At the first time in developing the software, there is no need for it to be perfect. It can’t be perfect on the first try. If you thrive for perfection for the first time it will take you longer to finish it and yet it still not sure if the sofware is perfect when it is finished. It will be better to finish the sofware quickly then just do it again and add bug fixes. It will save time and at the same time you will be able to know that the problems are easier because you have a running software that can be tested. The one who will use the running program would be the one to tell you what problems it has.

When building any program, you must be able to know what the program do. You must be able to look at the big picture and not yet at the details. Look at the overview of the program. Then make sample UIs by making sketches and choose which one is the best. Then do it in a real program. Make a real UI. The last thing to do is to code and finish it as fast as possible by doing those important codes for just to make it running. Finish it as fast as possible and check for bugs then fix them. It will be easier and faster this way since there is no need for you to think what will be the bugs that will be encountered since there is a real bug already from the running program.

When face to have a decision for a little detail or a little feature don’t let it bother you. Just decide quickly whatever it is. Don’t anymore think of the user of what they want. As long as that decision can be easily adjusted it will be fine. Let the users test the software. They will be able to tell you honestly what they like and what they don’t like.

Just Start on Getting Real… 5

Web development companies today, when they build and develop a web application, they put many and different features in the web application. They are thinking that the more the features, the better the web application will be. But in fact, it is the other way around. The less the features the application has the better. This means that the application should only have the most basic features or the most essential features. Companies must be able to tell what the most essential features in the application are. By doing this, the company can cost cut and not invest money on the features that are not needed or are not being used frequently. They can know what features to put in by listening to the people in forums or the like. There is one thing that they should keep in mind. Not all that are requested or posted by people should be put into the application. It is not the number of times that people requested for a feature that must be kept in mind. It is the frequency that the people are requesting. For example, there are 1000 requests for a feature A and there are only 100 requests for feature B. But the difference between the two is requests for feature A was only made for only a week. But the requests for feature be has been going for months. This means that people really want and need that feature since they keep on requesting for it. Companies will be able to tell what they need to add as a feature by not memorizing what is in the forums but just know and listen to them. Application should only be made with the essential features. Other features should be done by the people if they can do it or have another way for them to do it. This way companies will be able to save and people won’t have to deal with features that they don’t use.

Just Start on Getting Real.. 4

In this chapter, it tells that before starting to develop the application you must make or think first for a vision that will help you to make decisions.  To do this you must the purpose of the application, what makes the product different from other products out in the market.  Keep the vision as brief and simple as possible., There is no need to lengthen the vision. Even a sentence is fine.

When already starting the application, work big and from there go smaller. Always start big. Think of the big things that will greatly affect the application. Don’t mind first the  little details although they are partly important. Do them in the end when the more important things are finished.

This chapter also tells that one should not think of problems ahead of time. You must focus only at the task in hand. If problem come then that is the only time once should think of it. If one thinks in advance the possible problems more problems will occur and it will only delay the project since it take so much time to solve a specific problem that one still don’t have.

Also always remember that the appllication won’t always please everyone. Thus know your customers or your target market. When you already know the targeted market or customer focus on them and as much as possible please them.  Lastly don’t think or expect about people overloading the system.  Although it can be a huge problem, seldom had this problem been encountered. And when it is truly encountered, there is still time to fix it. This is good knowing that there won’t be any risk since if they did solve the scaling problem ahead of time but the application didn’t appealed well on the customers then they are just wasting time and money.