Our Project Management Methodology

Step 1

(Responsible parties: Key Project Stakeholders and Project Coordinator)

Kickoff Mission Statement Document: Defining a clear set of goals

The Mission Statement is the most crucial aspect of the project. It establishes a mutual vision of the product, website, or feature between the client and project coordinator. It's a stake in the ground that keeps the project focused on what's important to you as the project owner. The initial time constraints of the Key Product Stakeholders (you) are also captured at this meeting. Once complete, the Kickoff Mission Statement Document will be shared with the team and used to outline the objectives with approximate timelines.

Step 2

(Responsible parties: Key Project Stakeholders and Project Coordinator)

Researching and defining the audience

This task involves researching the potential users of the application, site or feature. We then write user stories as a means to better understanding how users will interact with the final product.

During this process we will define:

  1. 1
    Who the users are for usability purposes. First, we draft a set of characteristics and expectations of your expected users. This ensures that the application we build will be usable and appropriate for your target audience.
  2. 2
    Security and Access Requirements. This set of user stories defines the roles that need to be created as well as what access level these roles are given. During this process, we also create user stories defining how users will access information, detailing password policies, additional login in requirements, and more.

Step 3

(Responsible parties: Key Project Stakeholders and Project Coordinator)

Creating feature stories

This process starts by using the Mission Statement to define all the intentions of the web application and its features. These intentions are then broken down into smaller parts, which eventually become the feature stories within the different milestones (intentions) of the project. These feature stories provide us with a narrative look at how each feature of the application will work, and keep us focused on the overall goals of the project.

Once the milestones and feature stories have been completed, we use the MoSCoW Method to place a relative importance value on each of the features. The capital letters in MoSCoW stand for:

  • M - MUST have this.
  • S - SHOULD have this if at all possible.
  • C - COULD have this if it does not affect anything else.
  • W - WON'T have this time but WOULD like in the future. Alternatively, WANT.

These values help us to prioritize the workflow to meet the expected launch or deliverable date set by Key Product Stakeholders (you). It also ensures that our clients receive the core features needed for a successful launch, allowing us to continue adding features and

Step 4

(Responsible parties: Key Project Stakeholders and Project Coordinator)

Identifying existing web services to leverage

Not every feature has to be developed from the ground up. In some cases, a web service may exist that we can integrate with in order to reduce development time. A common example of this can be found in online payment gateways like PayPal and Google Checkout. These services can be integrated into our applications, allowing us to easily store and process credit cards for merchant exchanges. This works to decrease both our development time, and the liabilities associated with the application.

Step 5

(Responsible parties: Key Project Stakeholders, Project Coordinator, and Lead Developer)

Estimating and prioritizing the milestones

With all the stories in place and rated for importance, it's time for the Project Coordinator and Lead Developer to weigh in with a difficulty rating for each project milestone. Difficulty ratings are set on a scale of 1-10, based on how difficult it would be to complete a given milestone within a two-week timeframe. Using the importance and difficulty rating of each milestone as a guide, the Project Coordinator can then prioritize the milestones as part of a development outline. Key Project Stakeholders are then given the development outline for final approval.

Step 6

(Responsible parties: Key Project Stakeholders, Project Coordinator, and Lead Developer)

Breaking down the high level features into tasks

Breaking down the milestone features into smaller tasks is the start of the two-week Sprint period. During this planning phase, all the tasks needed to complete the feature are identified and given a time estimate. This task list is then made available online for the Key Project Stakeholders to view and track progression.

Step 7

(Responsible parties: Key Project Stakeholders, Project Coordinator, and Lead Designer)

Application Visual Guide, Design Layout, Interface Design, Wire framing

Whatever an application entails, in order for it to be successful, it has to be intuitive and easy to use. The interactions, interface, and application elements have to be conceived and developed with the app's specific user audience in mind. This inspiration is drawn from the research done in step two. Aligning design with the expected user base creates a positive user experience, which in turn turns users into repeat customers.

The first step in making sure that an app is user-friendly is storyboarding the user view designs needed to complete the current milestone. Designs are then reviewed by the Key Project Stakeholders, at which point revisions are made and a design is agreed upon. Once the final design is selected, the storyboard views are turned into tasks, given a time estimate, and added to the development outline.

Step 8

(Responsible parties: Development and Design Team)

Sprint Development

During this period the development and design team will take accepted sprint features and start the development process.

Step 9

Sprint Review

Upon the completion of the Sprint Development phase, an internal release is delivered to the Key Project Stakeholders for review. During this Sprint Review, the milestone tasks are demoed to the Key Project Stakeholders during a question-and-answer session. One by one, each completed task is demonstrated, allowing the Key Project Stakeholders to make notes and changes before final release.

Get in touch with Conceptzure to turn your possibilities into opportunities with a powerful custom web application.