Experience that yields results
Over the years we’ve honed and crafted a repeatable and flexible process that focuses on quick, iterative releases into test environments. A singular, holistic strategic foundation leads design and product definition. App level services are built ahead of UI development, all feeding back into design and constant stakeholder visibility. Robust QA ensures the right thing was built the right way then establishes user story functional test automation so that future changes can’t somehow accidentally break what has been approved and previously developed.
The absolute alignment of purpose and trust is something that creates greatness.
Jeff Sutherland is the father of Scrum process, he borrowed the term “Scrum” from an analogy put forth in a 1986 study by Takeuchi and Nonaka, published in the Harvard Business Review. In that study, Takeuchi and Nonaka compare high-performing, cross-functional teams to the scrum formation used by Rugby teams.
Scrum is the leading Agile development methodology, used by Fortune 500 companies around the world. It is the best methodology for Complex Project in the field of software development.
Scrum or Waterfall — We’ve Got Your Back
Each project can have unique requirements, and we fully appreciate that. Rather than rigidly imposing a one-size-fits-all approach, we meticulously analyze your business needs and suggest the optimal way to make your project succeed.
Since 2005, we have accumulated a wealth of expertise in many popular development methodologies, with Scrum being our weapon of choice. We also keep a close eye on, and adopt best practices from other agile methods, such as Lean and Scrumban.
Scrum is an iterative development model that uses time-boxed sprints. Scrum is best suited for larger, more complex projects that fit the following criteria:
Waterfall presupposes classic, linear development that relies on several project phases that do not overlap. Waterfall could be a good fit when:
What we believe
Partnerships work better
A collaborative, transparent relationship is key to successful product launch.
- Discovery & foundation
Seamgen strives to become subject matter experts in your business. By creating case scenarios and defining your users, we establish the requirements essential in moving forward. This process enables us to finalize a feature list and ultimately kickoff the project with project management, the design team, and the development team working collaboratively.
Weekly sprints & bi-weekly reviews
- Stakeholder & user interviews
We interview and gather requirements from subject matter experts, end users, and key business stakeholders to ensure we’re designing an optimal solution to meet their needs.
- Information architecture
Outline the overall architecture of the app, ensuring that we encompass both short term and long term plans and product goals. This is achieved by analyzing user flows as well as structural and navigational features.
Move quickly and test often with lightweight prototypes that highlight key interactions. This is an iterative process based on feedback, testing, and edits, typically with bi-weekly reviews of deliverables with the stakeholder and development teams.
- Prototypes & user testing
Outside of the core stakeholders and product team, the best way to get valuable feedback is to put the product in the hands of real users as features are completed.
- Visual design
Perfect the layouts created in wireframes and create a flexible and unique design system that works across multiple devices. Add moments of delight to expected behaviors with animations, transitions and fun interactions.
- User stories & acceptance criteria
Ensure that all epics and user stories are documented with acceptance criteria outlining all expected behaviors. This ensures that everything is built to proper specs as intended by the product team.
Our agile-hybrid development begins as soon as we have enough of a backlog of user stories and approved designs. We find it works best to have design completed ahead of front-end development. Part waterfall, part agile = agile-hybrid.
- Story grooming
Each sprint iteration begins with a grooming session, where stories are analyzed, improved if necessary, and divided up into tasks.
- Pull requests & builds
As tasks are completed, pull requests are issued and reviewed by other members of the team. Pull requests are merged with the build as they are approved.
- Design scrubs
Prior to the end-of-sprint demos, the design team reviews the latest build for completeness, satisfying design intent and expected behaviors.
- End of sprint demos
At the close of the sprint the development team demos their completed work to the client and the project team. All project stakeholders are invited to take part in the demo.
- Build releases
All sprints culminate with a build. You have instant access to the work that was completed. In the case of mobile applications, we use tools like HockeyApp and TestFlight to provide the application to all interested project stakeholders.
With sign off on all sides we’re ready to push to production and/or submit to respective app stores.
Test early and test often
- Test cases
QA begins writing functional test cases in Zephyr based on the prioritized functionality discussed in sprint planning, linked to relevant JIRA stories.
- Regression testing
This suite of tests will scale as the deployed functionality throughout the life of the project scales. This serves as the basis of the project's automated tests that run the deployments in every sprint.
Prior to the end of sprint demos, the design team reviews the latest build for completeness, satisfying design, and expected behaviors.
- Test on real devices
Execute all testing on real devices and operating systems relevant to the product so we see what your users see.
Transparent oversight is key
Your success is our success. We do everything we can to meet milestones and ensure deliverables either satisfy or exceed your expectations. Effective Project Management is one of the most critical aspects to project success as it ensures the following communication and milestones are met:
- Project & sprint plan
We create a comprehensive project sprint plan for both design and development phases of the project. We establish clear milestones, deliverables, and relevant stakeholders for each deliverable. This ensures that the project team knows what we plan to work on, in what order, and when we plan to review each milestone.
- Weekly project reports
Stakeholders will receive weekly project reports that recap what the team worked on, their hours, the budget for each team member, and any risks/impediments we’ve faced.
- Daily scrum
The team is in constant communication throughout the day. Project stakeholders are invited to participate as we cover: what was completed the previous day, what is being worked on today, and if anything is in our way.