
As we explained in our [previous post](Discovery-Phase-what-it-is-and-why-we-start-projects-with-it) the Discovery 
Phase of a new project is an important part of the project planning process. It involves researching 
and gathering information about the project to determine its feasibility, scope, and potential challenges.

### Typical Deliverables

The most typical deliverables of a Discovery Phase can include:

- **Project Charter**: The project charter is a high-level document that outlines the purpose, scope, and objectives of 
the project. It also includes information about the project's stakeholders, timelines, and budgets.

- **Business Case**: The business case is a document that provides a detailed analysis of the project's costs, 
  benefits, and risks. It helps to determine whether the project is worth pursuing and provides a framework for 
  decision-making.

- **Feasibility Report**: The feasibility report assesses the technical, operational, and financial feasibility of the 
project. It identifies potential risks and challenges and provides recommendations for how to mitigate them.

- **Requirements Document**: The requirements document outlines the functional and non-functional requirements of the 
project. It helps to ensure that everyone involved in the project has a clear understanding of what needs to be 
delivered.

### UX-related Deliverables

HelloWorld teams focus a lot on the usability and the usefulness of any new product having constantly the end-user in 
mind, so apart from the above they run a thorough UX analysis to help stakeholders evaluate their idea and steer the 
wheel towards the right direction before the Development Phase starts.

These are the UX-related deliverables HelloWorld experts work on during the Discovery Phase:

- **Personas analysis**: Personas analysis is a user-centered design technique used to develop a better understanding of 
  the intended users of a product or service. Personas are fictional characters that represent different user types 
  or user groups, based on data and research.

- **User-flow diagrams**: A user flow diagram is a visual representation of the steps a user takes to complete a task or
  achieve a goal within a product or service. It maps out the user's journey from start to finish, including all the
  touchpoints and interactions they have with the product or service.

- **User stories**: User stories are a tool used in Agile software development to describe a feature or functionality 
  of a product or service from the perspective of the user. User stories are short, simple, and focused on the end 
  goal of the user, and they are typically written in a specific format that follows the formula:

  "As a [user], I want [goal], so that [reason]."

  The user story format helps to ensure that the focus remains on the user and their needs, rather than on the
technical details of the feature or functionality.

- **Low fidelity clickable prototype**: A low fidelity clickable prototype is an early-stage design prototype that is 
  created using simple and rough sketches, wireframes, or other low-fidelity design tools. The prototype is designed 
  to be clickable, which means that the user can interact with it and simulate the experience of using the final 
  product.

  Despite their simplicity, low fidelity clickable prototypes can provide valuable insights into the user experience 
  of a product or service. By testing the prototype, stakeholders can identify potential issues and dead-ends early 
  enough and use this useful information to evaluate even better whether their idea worths pursuing or not and even 
  have a better picture about the end result.

### Conclusion

Overall, the deliverables of the Discovery Phase provide a solid foundation for the project. They help to ensure 
that everyone involved in the project is on the same page and that there is a clear understanding of the project's 
goals, objectives, and requirements.

Apart from that, deliverables such as the User Stories or the Clickable Prototype, prepare the ground for the next 
phases of the project, since they help professionals that will be involved down the road, grasp fast what we are 
trying to build and why.

By completing these deliverables, we can help to ensure that a new project is well-planned, feasible, and has the 
best possible chance of success while minimizing risk.

Cheers!!


Discovery Phase: deliverables


In our [previous post](discovery-phase-what-it-is-and-why-we-start-projects-with-it) we explained why the 
Discovery Phase is important and how much it affects projects' success. One thing we didn't mention though is that 
the Discovery Phase helps the team to evaluate the feasibility of a project in order to determine if it's worth 
pursuing in the first place.

Here are some crucial reasons why a Discovery Phase might lead us to abandon a project:

- One reason to consider abandoning a project during the Discovery Phase is if it doesn't align with the company's 
  goals or values. If the project doesn't fit into the company's long-term plans, it's better to move on early and 
  focus on projects that will help the company grow. Additionally, if the project goes against the company's values 
  or mission, it could harm its reputation and lead to negative consequences.

- Another reason to abandon a project during the Discovery Phase is if it's not financially viable. During the 
  Discovery Phase, the team should be conducting research to determine the potential Return On Investment (ROI) of 
  the project. If the projected ROI isn't high enough, it's not worth pursuing the project. Focusing on projects 
  that will generate a better ROI and help the company grow is better.

- Finally, if the team encounters significant roadblocks during the Discovery Phase that can't be overcome, it may 
  be time to abandon the project. This could include issues such as technical limitations or market saturation. If 
  the team can't find a way around these obstacles, it's better to cut their losses and focus on other projects.

In conclusion, deciding not to continue with the development of a new project during the Discovery Phase is a 
difficult decision, but sometimes it's the best one for the company. By staying objective and considering all 
factors, the team can make an informed decision about whether to continue or abandon the project. Ultimately, the 
goal is to focus on projects that align with the company's goals and values, have a high potential ROI, and can be 
completed successfully.

One of the core objectives of HelloWorld teams, throughout the Discovery Phase, is to help stakeholders evaluate 
products and projects so they can understand whether it's worth pursuing them.

Cheers!!


Discovery Phase: decide whether a project or a product is worth pursuing


Starting a new project can be exciting, but it's important to take the time to plan and prepare. A Discovery Phase 
is a crucial step in any project that involves User Experience (UX), Engineering and DevOps. This phase involves research, analysis, and planning that will inform the project's design and development. In this blog post, we will discuss why a Discovery Phase is important and how to get started.

Here are the reasons why a Discovery Phase is extremely important and should take place before actual development:

- The first reason to start a project with a Discovery Phase is to gain a deeper understanding of the users and their needs. A Discovery Phase involves user research, which can include surveys, interviews, and observations. By understanding the users' needs, pain points, and preferences, we can create a more effective and user-friendly product. This knowledge will inform the project's design and development, leading to a better user experience.

- Another reason to start a project with a Discovery Phase is to identify potential roadblocks and opportunities. During this phase, we will analyze the data and identify trends and patterns. This analysis can help us identify potential issues and opportunities that may arise during the project's development. By identifying these roadblocks early, we can develop a plan to mitigate them, ensuring that the project stays on track.

- The Discovery Phase is also an opportunity to establish a clear project vision and strategy. By gathering data and analyzing it, we can develop a project plan that is aligned with the core business goals and user needs. This plan will help guide the project's design and development, ensuring that everyone involved is working towards a common goal.

- Finally, a Discovery Phase can save time and money in the long run. By investing time in research and planning at the beginning of the project, we can avoid costly mistakes and redesigns later on. By establishing a clear project vision and strategy, we can ensure that everyone involved is working towards the same goal, reducing the risk of miscommunication and delays.

In conclusion, starting a project with a Discovery Phase is an essential step for any project that involves UX, Engineering and DevOps. By gaining a deeper understanding of the users and their needs, identifying potential roadblocks and opportunities, establishing a clear project vision and strategy, and saving time and money in the long run, we can ensure that the project is successful.

HelloWorld highly advises its customers to start all new projects with a Discovery Phase, so we collaborate closely to plan, analyze and prepare the core business needs and ensure that we are about to create a successful and user-friendly product.

Cheers!!


Discovery Phase: what it is and why we start new projects with it


Working in the field of technology requires endless development and constant growth. This applies both to each employee individually and to the company as a whole. To this end, every six months we conduct reviews of different kind.

## Mid-Year Review

The mid-year review is aimed at self-analysis of each company member regarding their qualities, skills and habits. Each employee receives a personalised questionnaire to fill out.

After the completion of the survey, a 1:1 is conducted with the goal to discuss results, goals and conclusions. The results of the review are private, and shared only with direct management.

The mid-year review is conducted twice per year every January-February, and every July-August.

## 360&#xb0; Review

The 360&#xb0; review aims to help employees of all levels get feedback from colleagues, management and subordinates. Each employee receives personalised questionnaires to fill out.

After the completion of the surveys, a 1:1 is conducted with the goal to discuss results, goals and conclusions. The results of the review are transparent, so every feedback is delivered directly with names disclosed.

The 360&#xb0; review is conducted once per year every January-February.

## HelloWorld Review

As simple as it may seem, the company also needs its people feedback. Each employee receives a general questionnaire to fill out. The results of the review are private, and shared only with upper management.

The company review is conducted twice per year every March-April, and every September-October.

You can find it here => [https://docs.helloworld.gr/docs/reviews.html](https://docs.helloworld.gr/docs/reviews.html)

Enjoy!!! 😉


Reviews


Everyone is talking about culture so culture seems to be everywhere nowadays.

Culture for hiring, culture for working, culture for delivering, culture for speaking, culture for listening, culture for collaborating, and many more.

What is culture though? Is it the way we behave or we think? Is it the way we work and we collaborate? Is it the level of results we provide or the impact our team has? Is it the way we behave and we communicate? Is it the way we dream and set higher goals every single day?

So what is an organization's culture all about? Can you put it on paper using simple words to describe it?

This is what we did by issuing our manifesto divided into two main pillars:

- principles for our individuals

- principles for our teams

You can find it here => [https://docs.helloworld.gr/docs/manifesto.html](https://docs.helloworld.gr/docs/manifesto.html)

Enjoy!!! 😉


Our Manifesto


Using old and inefficient techniques like [waterfall](https://en.wikipedia.org/wiki/Waterfall_model) while building modern software applications can become extremely dangerous in today's fast-paced business environment.

The main reason is that competition is enormous, things change lightning fast so businesses and IT teams need to find ways to work closely, maintain their flexibility and adapt fast.

[Extreme Programming](https://en.wikipedia.org/wiki/Extreme_programming) is a great recipe that solves these issues and helps us to build complex and useful applications while maintaining strong collaboration bonds with our customers. Let's see why.

## The problem

As an IT team, how often do you come across new requests from the customer's side that force you to refactor heavily or do things from the ground while a project runs?

As a customer, how often do you realize that you actually need something different compared with the things you asked for upfront while a project runs?

## Business needs are doomed to change

We need to realize that we tend to build even more and more complex software applications so not being able to predict everything upfront is quite possible to happen.

Actually, this is the most common one.

So the 1.000.000 dollars question is "How can we describe, estimate and foresee all these things that are not known or described in full detail yet, and might be required in the near future?"

We simply cannot!! We are not wizards that can tell the future, right?

## The solution

[Extreme Programming](http://www.extremeprogramming.org) is an approach that helps hugely to minimize this risk and bring the 2 worlds closer.

This Agile model helps us have small iterations, work side-by-side with the customers and adapt fast to their growing needs without worrying about error-prone estimations, newly introduced requirements, or last-minute changes.

With XP methodology we can provide value to our customers constantly while adapting to various requirements that were not visible or even described at first.

XP improves a software project in five essential ways:

- communication
- simplicity
- feedback
- respect
- courage

Through these principles, customers and IT people come closer, build stronger bonds, stay constantly on the same page and work for a common cause all the way long.

Let's build useful stuff together then. Cheers!!


Business and IT teams, stop arguing and start collaborating


The most valuable asset of every organization is its people. That said the hiring process plays a crucial role into finding talented people who match perfectly with the organization's culture.

Apart from that, the hiring process actually is the start of the journey, so it speaks volumes regarding the organization's ethos and values. Who wants to make a bad first impression, right?

So how do we check for perfect matches?

### Use the right tools for the job

We are using tools like [Workable](https://apply.workable.com/helloworld-pc/) to publish and manage our openings.

Platforms like [LinkedIn](https://www.linkedin.com/company/helloworld-pc/) and [Facebook](https://www.facebook.com/helloworld.gr) are used to demonstrate them to the world.

### Curriculum Vitae scan

A CV cannot describe accurately a talented person, but it can provide some very important details about their background, their interests or even their personality.

Things that stand out:

- cover letters with a personal flavour
- involvement with open source projects
- hobbies, interests and activities outside of working hours
- social profiles
- the general feeling that the CV is prepared with ❤️

Why such an interest about social profiles, hobbies and activities?

This is because we are looking first for a human-being that can fit into our team and then for a professional who can do the job.

### Assignment

The very next step is a short technical assignment that lasts less than one (1) hour. Through this assignment we verify that the candidate has the technical knowledge required for this position.

There are tons of online platforms out there that provide excellent tools for this job and help us to automate it as much as possible.

Things we evaluate:

- soft skills questions, so we spot matches
- ability to solve algorithms with any programming language
- deep knowledge of the technologies in question like ReactJS, HTML, CSS, RESTful APIs, MVC, OOP etc

### Interview

At this stage a thirty (30) minutes interview takes place, so we get to know each other, discuss things that are not mentioned in the CV and analyze the assignment's results.

The candidate asks things about the organization's vision and goals while we try to see whether we are a good fit and vice-versa.

It is important to have a match for both sides in order for this marriage to become a functional one.

### Work together period

This is the final stage during which candidates work side by side with some of our people on actual stories and tasks. This period lasts for one (1) week and in the end we evaluate all this together with the candidate.

Through this process, candidates can see what does it mean to work with us in order to eliminate the possibility of any unpleasant surprises after getting hired.

We definitely don't want to waste peoples' time, so candidates are getting paid for their precious time and efforts before getting involved in this process and not after.

Let's make it work then. Cheers!!


The hiring process is where the organization's culture begins


Because of our involvement in various early-stage startups, we come across some repeated patterns and common pitfalls quite frequently. That said, we decided to put together and share publicly some tips and best practices to help people with brilliant ideas turn them into useful products.

To validate fast a new idea and minimize costs, there are some critical things to consider in order to minimize time to market, reduce costs and stay focused all the way long.

### Strip down the idea and focus on its core concept

Trying to add all these bells and whistles is slowing down your progress, disorientates you, and forces you to lose focus eventually.

Stay in the course by putting all the eggs in one basket.

Stick to the core concept of your idea and try to ship it.

### Do heavy Research and Development cycles early enough

It is important to do some meaningful research and Development early enough before creating any design or writing any piece of code.

Check competition, investigate legal matters, speak with experts in the field. In general, try to spot flaws and holes in your plan.

All these will be extremely beneficial since you will end up having a very clear vision before starting the actual implementation.

Not moving forward due to various issues that might come up at this stage, might also be a great decision that will save you further efforts, money, and time.

### Avoid over-engineering

Ok, we all love technology, fancy libraries, and state-of-the-art frameworks but here we are trying to launch a new product and this is all that matters. Work smart and focused.

Sometimes a clickable prototype might be all we need to validate some patterns, demonstrate our idea, and avoid premature development cycles.

### Keep it simple

If you decide to create a Proof of Concept, then keep the technology stack simple to reduce complexity, cost, and time-to-market.

There is no need to create a complex setup with N services and User Interfaces to present your idea to the world.

Use the technologies you are familiar with and be ready to rewrite from the ground this PoC with a more complex technology stack once the idea gets validated or even throw it away if it doesn't.

### Make it solid

Simple doesn't mean sloppy or buggy.

Ensure that the core concept is bullet-proof and pretty well-tested so that early users can really use it and provide meaningful feedback.

### Validate the idea by getting honest feedback asap

Try to ship fast in the market, so you get actual feedback fast and re-iterate accordingly.

Don't be afraid to get honest feedback from actual users out there.

Even if the feedback is negative, it will help you to reshape your idea and move with a better plan ahead.

### Find a mentor

The competition out there is huge and the challenges you'll need to overcome can be tough.

Sometimes you will be forced to step out of your comfort zone a lot.

Find an experienced mentor that can stick by your side and will support and give you valuable advice throughout your journey.

### Find the right partners

The more your idea will mature the more you will need people with different skills and expertise than yours.

These might be UX experts, software engineers, architects, marketing or sales professionals, and so on.

Don't be reluctant to partner or even hire the right people that can work by your side in order to step up your game.

### Be patient

The world was not created in one day neither your idea will be.

Be patient, stay focused, and above all have fun.

Your idea is a newborn kid that is growing before your eyes.

Try to be a patient parent and enjoy the adventure.

Cheers!!


Publications about "entrepreneurship"

By HelloWorld PC

Discovery Phase: deliverables

By HelloWorld PC

Discovery Phase: decide whether a project or a product is worth pursuing

By HelloWorld PC

Discovery Phase: what it is and why we start new projects with it

By HelloWorld PC

Reviews

By HelloWorld PC

Our Manifesto

By HelloWorld PC

Business and IT teams, stop arguing and start collaborating

By HelloWorld PC

The hiring process is where the organization's culture begins

By HelloWorld PC

Start small, grow big