Unity

According to the book, companies separate designs, development and other sections in making web apps. I think it’s ok to separate those so they can divide the work and in order for the group or team to finish  and integrate it on time. Separating designs, and others is ok and in fact it can help them but they have to remember that even though they separate those things, there’s a possibility to have lock of communication. For me, one member must work with other members. They must consider communication; member must support other member for them to integrate their finished output.

Alone time

I agree to getting real. Everyone needs to be alone sometimes. They need to find their own “zone”.  The “zone” is where they can do work on their own. Here, they are more focused and don’t think There’s a time that people should be alone to get things done. Once they’re alone, they can do more things properly and do what they have to do. In this way, they become productive and ready to finish their work.

Meetings are toxic

Having a meeting is good as long as it has sense. People conduct meeting because they want clarification regarding to something. But the question here is do they really have go to meeting just because they have to clarify things? I think meting is ok. You can conduct and attend meeting. Meetings are good. I can attend meetings if and only if there’s an agenda. Aside from that meeting should not take long.  30 minutes is enough for meetings. But you know, instead of meetings, why don’t you discuss it via im or emails.

Seek and Celebrate Small Victories

According to getting real, it’s ok to celebrate small things because it increases you motivation. Motivation is really important especially when you’re working. Without motivation, I think you can’t do things properly or the output won’t be good as that. I agree to getting real. You must celebrate small things as long as it motivates your people.

Running Software:
I think this is the most excited part in developing an application. It’s amazing if your application runs smoothly and bug- free. the real action will only start when you run your software correctly. for me, we have to consider it at the very first time. we have to think of a way on how we can run the application even though it’s not that complete in some way.

Work in iteration:
I agree with this idea. For me, it’s ok if we don’t get thngs right the first time. Once we go through the process of creating the application, that’s the only thing you can say that you truly understand the application. Aside from that don’t try to make things perfectly. try to do first what you can do to your application. You will only see the changes and understand your application if you allow it to grow and do things one at a time.

From Idea to Implementation
Before you develop an application. You must get the requirements, define and modify, then analyze things properly, design the application, code it, implement it, test it, lastly maintain it. In a team, brainstorming is the first step before you can make an application. You must create first ideas before you can implement an applicatios. After that, it’s time for you to make sketches. Sketch are ideas. Start building screens. You are free to write anything since there’s no wrong and write answers. It’s your own ideas after a’ll. When you’re done with the sketches, it’s time for you to code. Then make a beta verion before you release it.

Decisions

Decisions are important in making an applicatiions. We must considered decisions in everything. It’s ok to have wrong decisions. We can  change and revise it easily. In releasing the application, we must decide whether we create a beta version or not.

I think the main point or the idea on this chapter is making sure that you stick with what’s important or needed. Select features or create features that are needed and necessary to your application. Don’t put things that are not needed to the application. Stick with what is important. Don’t make things badly. Application must be easy to use. Don’t put features that are not important or doesn’t have any value. If you want to do that, better to drop it or remove it before you deploy your apps because when you continue it, you’re just wasting your time adding up features that aren’t supposed to be in your application. Aside from that I do agree on the idea that you better learn to say “no” to any client. It’s alright to put features, but you must understand why you put those features in your application and you must know the consequences on making that. You must realize that costs, time, and simplicity are factors that everyone must consider. It’s ok to put features in your application but make sure that the features you included are important and useful. It is better to create an application that is simple and usable. When I read the whole chapter, you may say that the information is true. In selecting features for example in an inventory system, consider that it should be able to add data at the same time updating it, can delete data whenever they want to delete it, and others. Make it simple so that the one who will use your application will understand it easily. Then, you must realize and know that you better say “no” in selecting features. You must learn how to say that word because it has a big impact when it come to feature selection. Say no will lead you to become productive and to come up with a good application. Remember that saying no is ok and it’s better if we say no.

Chapter 4 talks about knowing your vision  why you are doing such application, and how to prioritize and manage things properly. In making an application, you need to identify your vision first because this will be your guide. Your vision should answer this questions: Why did you come up with this kind of application? What’s the purpose of this? You must know your application. Then, after knowing it, set things first before you start doing your application. You have to make priorities in order for you to achieve what you want to achieve for your application. In this chapter, it emphasizes how important priorities and focus are  in building application. Focus on one part before you move to another. Before you achieve the whole thing, you must do the first step. Then, don’t do it by batch. Don’t get all the details because you might be confused.Then, focus on what the customer really wants.