It’s all in the details.  At BlueFletch, we don’t shy away from dedicating the time and resources needed to fully understand your solution and provide guidance in choosing the right technology.  From technical architecture to security specifics, we partner with you to ensure comprehensive requirements are captured for planning and traceability.

Gathering and reviewing requirements at the onset of a project is critical to identifying, understanding and solving the right problems and to support successful development and delivery.  We use a variety of approaches and tools: ride-alongs and shadows, interviews with stakeholders, white boarding, process mapping, etc.  The requirements process is the planning stage necessary in order to enter the design process with momentum and minimal back-and-forth.  The easier our team can reference and understand requirements, the higher our efficiency going forward.

First steps

Do you have a problem that you are ready to solve?  We will scope out the effort and provide project roadmaps and estimates.  Our requirements process begins as soon as your end goal, product or solution is communicated with us.  We research the line of business, competitors and mine similar projects we’ve worked on for insights and potential risks.

mobile app project roadmap

Meetings

Our initial effort is to prepare a rough index of user stories and apply best practices and past learning to create initial artifacts on which to collaborate with stakeholders.  We then schedule requirements and design meetings, usually limited to five or fewer stakeholders and decision makers relevant to the session’s topic.  Limiting sessions to a manageable size reduces tangents and allows thorough understanding and documentation to build an exact solution.

During the sessions, there are often open questions and takeaways for the group.  Not everything has to be solved in one sitting.  There is great brainstorming that occurs when your idea is deeply analyzed and we are sure to capture all notes for future use.

After the meeting

The output of the requirements process is technical workflows highlighting integrations, user workflows, technical architecture diagrams and our master requirement tracking file.

Not only will these artifacts assist in your decision-making, but they will also be the reference for our project planning.  We create development and quality assurance tasks based each user story’s requirements.  Functional or non-functional, every requirement should be captured and tested.

Continuing into the project lifecycle, requirements will evolve. They are then updated and revised to match new discoveries and design decisions.

Mobile Strategy Workshops

If your organization is looking to accelerate their mobile projects, we provide a free mobile strategy workshop covering a variety of topics tailored to your specific interest areas. A mobile strategy workshop is an opportunity for your team to pick our brains about our experience developing mobile solutions. Past workshop topics include: development tooling, hardware interaction, UX design approach, deployment process, and domain specific mobile principles (retail, logistics, and warehouse). To learn more about our free mobile workshops, learn more here.

Related Posts

Patrick McGlynn

Patrick McGlynn

Mobility Consultant - Patrick graduated from the University of Georgia with a B.B.A. in Management Information Systems. He joined BlueFletch with four years consulting experience in data warehousing. He specializes in data analysis, integration, and business intelligence throughout a variety of industries.