This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
In this battle, I’ve found a secret weapon hidden within one of our core engineering strategies, an idea called Run Less Software. As well as being a critical philosophy behind how we build software, it also represents how I feel about the software industry and technology in general. Choose standard technology.
Many CEOs of software-enabled businesses call us with a similar concern: Are we getting the right results from our softwareteam? We hear them explain that their current softwaredevelopment is expensive, deliveries are rarely on time, and random bugs appear. But everyone’s situation is unique.
I wrote a variation of this for the various product teams at Whispir recently and then as fate would have it, a CEO I know reached out to me on LinkedIn asking the same thing?—?so with very little effort but a huge amount of diligence and thought, and you can do it in 15 minutes if you have access to all the research already.
I love that Marty Cagan and Jeff Patton have long been advocates of dual-track development. If you aren’t familiar with dual-track development, it’s the separation of product discovery from product delivery. User stories and user story mapping help a team align around the top priorities and get clarity around what they are delivering.
For many years CSSSR has been developing IT systems for the biggest online banks, witnessing their success firsthand. This experience has led to several key insights: You Don’t Need a Large IT Department “We operate in small teams. To begin with, the development of new functionality requires considerable resources, including people.
A common question for product managers, project managers, technical program managers, and softwaredevelopers alike is what methodology to use given a project. Which should you and your teams decide the utilize? Whichever methodology a team operates under will heavily influence how they work and communicate with one another.
But one thing technology leaders need to ask themselves is, “what are the threats we face?” The news is filled with tales of hackers breaking into financial institutions, DDoS attacks on credit card companies, and data breaches due to poor software configuration. Phase 1: DueDiligence and Discovery.
Where are product teams getting their feature ideas? Most concerningly, 19% of respondents reported that their top source of ideas comes from senior management, who are often disconnected from both customers and the product development process. Why do product teams become feature factories?
So, to safeguard ePHI (Protected Health Information) from cyber attacks, healthcare organizations and medical softwaredevelopment companies are imposing strict HIPAA compliance regulations. The entire risk analysis is documented and reviewed periodically to prevent ePHI violations. More: HIPAA-compliant web hosting servers 4.
Here’s what a comprehensive security assessment looks like: Step 1 – DueDiligence. You document information about the people, processes, and technologies that affect the organization’s overall security framework. SDLC (SoftwareDevelopment Life Cycle) of the organization . The Security Assessment Process.
Arkenea is a trusted, exclusively healthcare-focused softwaredevelopment firm with 13+ years of experience. But these companies opted for several developers for innovating applications for different applications. Make a New Class Develop a new class and save it as a message’ or something similar.
JJ is also a serial entrepreneur, co-founding a healthcare technology company as well as a product development and talent management consultancy. Most often when I am looking for content on product management, I find content centered around how to make great software and technology products. How to prioritize a backlog.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content