PiSrc was founded in 2018 bringing 20 years of experience working with S&P 500 companies across the media, retail, financial, healthcare, manufacturing, and non-profit sectors. Our aim is to bring state-of-the-art capabilities predominantly practiced by cutting-edge startups to traditional enterprise organizations.
We are a tech-centric company that believes the best ideas should win.
We see people as the primary drivers of success, not processes and rigid hierarchies.
We prefer to operate in small high-impact teams rather than large brute force programmes.
We value ingenuity, passion, and focus.
Our work is guided by experience, usability, and sensible design.
Our mission is to bring back quality programming to create solutions that work
We love the big picture, and strategy, and ideation, and shoot-for-the-moon ambition... here's how we get there.
Learn about how we work by interacting with each bubble.
We introduce developers early in the planning process before the requirements are written. By getting developers to engage earlier and collaborate with stakeholders, we increase root understanding and are able to deliver solutions that address the business problem with the best software engineering approach. Requirements are hashed out during meetings, translated into technical requirements by the development team and approved by the stakeholder.
Keep it Real
We are drawn to the latest frameworks, data structures, and libraries, but we make sure every solution connects with the needs of the project and the people that will ultimately support and extend the work product. We value innovation, but we also don't like to reinvent the wheel. There is no cost to change, and so we frequently ask of our technical decisions:
Achievable Outcomes, Steady Change
We avoid big-bang programmes and vast digital transformation initiatives. Before committing to a new approach, we reduce uncertainties by creating prototypes and increasing confidence through proof-of-concept demos. It is with years of experience and numerous engagements that we hold a deep respect for the complexities and unique qualities of each business. For this reason, we try to size our projects into manageable efforts between 6-8 months. We prioritize work with maximum impact and minimal perturbation.
When we hear of a change in the requirements, we understand that someone has realized how to make a thing better. Of course, there are timelines to follow and plans to adjust, but we'll talk it through, adjust priorities, and make the best decisions.
Radical Quality
We understand the rapid pace of business. We also understand the deep cost of failure and poor implementation. When people talk about quality, there is an emphasis on defects, missed requirements, and broken pages. We agree. But when we consider quality, we also consider true software craftsmanship. We ask ourselves:
We ask ourselves these questions as we plan our solutions, when we conduct code reviews, and before we hand over deliverables. Profuse documentation is an important part of our attitude toward transparent code, and our desire for our customers to sustain development after the engagement. Perfection has a long tail, and we assume the solution will continue to be improved as you learn more, adjust, and tackle new challenges.
Radical Quality means more than avoiding mistakes. It means doing things correctly the first time. It means being ready to be successful.
These are the approaches that have brought success in the past. We believe they will guide success in the future. But ultimately, we don't rigidly adhere to methodologies or hold pocket manifestos about the right way to do things. All process needs to serve the people who ultimately deliver the solution. We will adjust, find a process that works, and push toward a win-state to deliver a quality product.
This high-level engagement structure represents a starting point, but like everything we do, How We Work depends a lot on How You Work. We want the process to make sense, reflect the contextual realities on the group, and always serve the greater purpose of leading you toward that win-state.
Talk with the right people, review current tools and systems, and define the problems.
Identify gaps in tools and processes, simplify and normalize areas of concern, run POCs, create an integrated solution blueprint.
Allocate resources, reconcile dependencies, assign tasks to sprints, establish critical milestones for on-time delivery.
Sprint development cycles.
Functional and integration test script execution. Performance and scalability tuning. Usability feedback.
Show progress to stakeholders. Integrate feedback and testing results to iteratively improve the solution.
Connect the solution to external systems.
User acceptance and testing.
Go Live.
Check analytics and logs. Identify opportunities for improvement.
Train and educate internal teams.
Long-term partnerships and enablement.
