Overview

In this lesson, we are going to analyze the “Project Execution” feature. This is a quickly way to review the application that will help the project team members to create defects or add/modify controls inside the page that we are working on.

Let’s check how automatically the revision can be added into the project’s requirement as pending task with this feature.

How to execute a Project in Wayfast?

To begin, let’s make sure that we have an active requirement inside our project. Focus on “Project Execution” header icon

Open

Automatically the “Project Execution” tab is displayed as initial screen. There’s only one dropdown field where you can select the execution type between 2 options:

• With Pencil: this option will run the preview showing a highlighting pencil on each object inside the page to make some notes and add some new tasks for the team.

• Without Pencil: this is the same preview that you can use on every page generated to verify that the objects added into the screen are displayed like it’s expected.

In this example, we are interested on analyze the application using “With pencil” option to generate new requirements or bugs on the application.

Open

Once we select “With Pencil” option, let’s execute the application clicking on “Run” button

A new tab is opened with the application displayed on the screen. Mouseover the “Inputbox” control and we will see the pencil icon available. Click on it and a popup window is going to be prompted.

Let’s check the properties inside this popup

Comment on control

Now that we learnt how to execute and review using “Project Execution”, in the following lesson, we are going to analyze how these 2 possible scenarios can be added into the development.

Create a “New Control” task based on Project Execution

Once we click on “Pencil” icon to make a comment over this control, select “New Control” option.

We need to include the position of this new control that we want to add. Make a brief description that will help the developers to understand this action item and include the estimation size, developer and criticality. Also we can put a comment in the description to provide more insight on the requested item.

Click on “Submit” button

If we want to verify that the requirement is created in our project, let’s go to “Requirements” section

Automatically we can identify the object as Bug inside the “Pending Tasks” bucket and also it’s listed at the left navigation bar. Click on task’s details and we can verify that all the information is the same saved from the Project Execution feature.

In case anyone in the project wants to work on the task, check it and turn it active.

Create a “Modify Control” task based on Project Execution

In this example, once we click on “Pencil” icon to make a note over this control, we will select “Modify Control” option.

We need to choose between “Bug” if there’s any defect inside the control or “Requirement” in case you want to make a change request. Again, it’s important to add a detailed description that will help the developers to understand the task and include the estimation size, developer and set the criticality before submit the request.

Click on “Submit” button and turn to “Requirements” section

Requirement dashboard will display the object as Requirement inside the “Pending Tasks” bucket and also it’s listed at the left navigation bar. Click on task’s details and we can verify that all the information is retrieved from the Project Execution feature.

Recap

Using the “Project Execution” feature, we can manage our project and delivery new tasks by simply navigating through the application. We can have a better traceability over the new items or reported defects that are part of the development process.