9 answers
9
Asked 706 views

What am I supposed to consider on starting a technological project?

Any technological project

college technology
Answer This

+25 Karma if successful
From: You
To: Friend
Subject: Career question for you
9

9 answers

3
Updated
Share a link to this answer
Share a link to this answer

Ryan’s Answer

This is highly dependent upon the project and problem(s) that you're trying to solve, but here are some starting questions/prompts that could be useful:
- What do your users expect in your project/solution?
- What is the minimum viable functionality that you can provide?
- How can you break the project into logical "chunks" so that you can make changes to your project incrementally? For example, building a forum might have a "add ability to make posts" step, a "add support for users logging in", etc.
3
0
Updated
Share a link to this answer
Share a link to this answer

Arian’s Answer

Hello Alejandro, you know you must consider several aspects when starting a technological project, such as technical and economic feasibility, the necessary resources, development time, the work team, data security and privacy, scalability of the project, regulations. legal and the satisfaction of user needs. It is also important to take into account innovation and competition in the market, as well as the long-term sustainability of the project.
0
0
Updated
Share a link to this answer
Share a link to this answer

Rahul’s Answer

Alexander,

I would ask you to consider following things:
1. Why are you building something?
2. What is it you are trying to build?
3. What are the things at your disposal to build it?
4. What are the things you need to acquire to build the things?
5. How are you going to utilize the things at your disposal (you own or acquire) to build?
6. Does it make sense to build stuff economically( financial/time/resource) investment?
0
0
Updated
Share a link to this answer
Share a link to this answer

Adekunle’s Answer

Hello Alexander! I would start with what you're interested in- do you like mobile apps? Or are you interested in websites? How about building physical things? You can start there work backwards by learning the technologies that are used for your specific interest.
0
0
Updated
Share a link to this answer
Share a link to this answer

Michelle’s Answer

I agree with Ryan that it's highly dependent on the problem to solve. There are a few additional questions that may be helpful:
- What problem am I trying to solve?
- Are there existing technology solutions that solve that problem? If so, what about them isn't optimal? What things work really well?
- What piece of the problem do I want to focus on?
- Ask for feedback about your idea. Ask friends, ask family, ask colleagues, and listen. Adjust your approach based on their responses.
- How can I prototype this without a lot of technology to prove out the concept? Use the minimum viable product approach. See the Zappos MVP origin story as an example of very lean conceptual bootstrapping.
- Once you've shaped your desired solution, break it down in the smallest possible steps. Look for existing tools that help you get started. Are there some low-cost, low-barrier to entry tools you can use to mock up your solution?
0
0
Updated
Share a link to this answer
Share a link to this answer

Jason’s Answer

Start with the end in mind. What is your goal? Is it to learn a new technology? Build the next social networking site? Fulfill a need in your parents business? Then, consider what this solution might look like and plan it out on paper. Then, try to break the solution down into individual steps that need to be completed in order to build out your solution. Don't get frustrated if you run into issues. Even professionals do! If you find you are are passionate about technological projects, go to school for it and learn as much as you can!

Good luck Alexander!
0
0
Updated
Share a link to this answer
Share a link to this answer

Layne’s Answer

This is a great question. Many people learn by trial and error, but the great news is that most successful projects will follow a similar framework. Both technical and non-technical projects will follow the same steps. The main difference with technical projects is that they may require some additional knowledge or contributions related to the technical work. The first step is establishing the purpose of the project. This can be a problem you are trying to solve, a product you are trying to build, or a major task you are trying to complete. From there, you inventory your available resources and the people who may be involved in the project. You meet with stakeholders, and agree on the purpose of the project and the plan. Then you will set reasonable milestones and key dates in your timeline. It will be important to help all team members keep track of these milestones and ensure that everyone is able to meet the set dates. You may need to adjust timelines for unexpected obstacles. That is okay. Just repeat the steps, and then continue to work to your timeline. Once complete, it is always important to do a debrief. Identify what went well and celebrate that. Also identify areas of improvement that you can apply to future projects. Be sure to thank and celebrate everyone who contribute to making your project a success.
0
0
Updated
Share a link to this answer
Share a link to this answer

Anmolpreet singh’s Answer

Here are some important points to think about:
1. What is the project you're working on?
2. What is the purpose of your project?
3. What strategy will you use to construct it?
4. Is there a ready-made solution available that could solve your issue?
5. Has someone else already found a solution to this problem? Often, there might be existing templates or best practices that you can use. If so, these could be a good reference.
0
0
Updated
Share a link to this answer
Share a link to this answer

Rafael’s Answer

Hi Alexander! For a tech project, project, it’s essential to conduct a thorough needs analysis to understand the market and user requirements. start with a deep dive into market and user needs. Set clear goals and scope, then map out a solid plan with timelines and goals. Choose the right tech, build a great team, secure funding, and plan for risks. This holistic approach, focusing on both technology and user needs, will guide you towards a successful project outcome. Best of luck!
0