Technical Product Management

Technical Product Management
Which of these certifications is important to you when hiring a software tester? Choose all that apply.

Top Answer: When I was at E&Y, when the partner was asked if we had CISSP certification, he replied “no, but focus on their experience”.  After we all got certified, he started replying: “yes, but focus on their experience”.    The IT industry love certs. But what counts is experience.

If you had a magic wand - what's the #1 daily business challenge you'd eliminate?

Top Answer: Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.

Where should product managers fit in the org structure?

Top Answer: I believe the broader organizational strategy or construct is important to architect and would then inform where product management as a function fits. I have operated in organizations where product management was part of stand alone function, was part of marketing, was within engineering, etc. Similar to most other organizational models, where the function sits is important but it is far more important that the collaboration, empowerment, decision making process, alignment with engineering, etc is clear and working effectively. 

Related Tags
Deployment Testing: Tools and ChallengesDeployment Testing: Tools and Challenges

How do tech leaders navigate the test phase of deployment?

If you are a current SAP customer, when do you plan to migrate to SAP S/4HANA?

Top Answer: No plan to migrate soon.

Related Tags
People & Leadership
Strategy & Architecture
End-User Services & Collaboration
Applications & Platforms
Governance, Risk & Compliance
Data & Analytics
Business Intelligence
Disruptive & Emerging Technologies
Team & Organizational Design
Security Strategy & Roadmap
IT Strategy & Roadmap
Outsourcing & Managed Services
Backup & Disaster Recovery
Public Cloud
Hybrid Cloud
Contact Center & Telecom
Data Center
Device Management
End-User Devices
Productivity Tools
Collaboration Solutions
Document Management
Business Applications
Human Resources (HRIS)
Technical Product Management
Software Development
Quality Assurance
Continuous Integration/Continuous Deployment (CI/CD)
Enterprise & IT Service Management (ITSM)
Availability & Capacity Management
KPIs, Metrics & Reporting
Financial Management
Vendor Management
Service Desk
Management Tools
Risk Management
Data Privacy
Artificial Intelligence & Machine Learning (AI/ML)
Data Warehouse
Security & GRC
Identity & Access Management (IAM)
Peer Insights
Vendor/Product Recommendation
Business Continuity & Disaster Recovery
Crisis Management
Customer Engagement
Customer Relationship Management (CRM)
Enterprise Resource Planning (ERP)
Business Relationships
Talent Management & Performance
Portfolio, Program & Project Management
Data Management
Big Data
Vendor/Product Assessment
Process Management
Asset & Configuration Management
Operations Management
Mobile Development
How do you define R&D in the context of software development?

Top Answer: I've noticed that many CTOs don't have much experience defining what classifies as R&D. The strict term is: starting an endeavor in which you are unsure of the result. Adding new features to an existing product isn't R&D. Developing your company's version of a product when there are already many in the market is probably not R&D; but trying to do a moonshot change to your product probably qualifies. Machine learning (ML) and artificial intelligence (AI) areas do generally fall into R&D because you don't know whether it's going to work. That's the general idea: If you don't know whether it's going to work, it's R&D.

Related Tags
Why do so many startups fail within the first two years?

Top Answer: Ideas are a dime a dozen and that's why a lot of startups fail within the first two years: they cannot get past the ideation phase to execute and test the market. I listen to at least two pitches from founders every week and I see how persistent they are. Are they going to follow up? Or will they just pitch and then they're gone without ever following up? There's a lot of innovation happening, but it's all what I call ephemeral innovation. A lot of these ideas die out because they cannot get past the pre-seed stage, or even making a prototype and testing the market. The startup market is flaky but that's how innovation happens. The cream rises to the top and if you are lucky enough to get the support of investors and the market, you can build something more permanent than a one year deal.

Application Architecture AgilityApplication Architecture Agility

As business needs change rapidly, Pulse surveys 100 IT and engineering leaders to find out if their application architecture, systems, and integrations can keep up.

How do startup founders know when a pivot is needed?

Top Answer: There are micro and macro pivots in businesses, and you want to make sure you are intentional about it either way. Don't do it because you think, “My competitor's doing this, so I have to do it.” Be deliberate about whatever adjustments you make to your strategy or execution. You will make some major macro pivots at some point, but those changes don't happen every day. Micro pivots could happen every week. If a competitor puts out an ad, for example, maybe I’ll want to change my marketing messaging. Macro pivots could happen if there's a gap in the market for our product. Then we can repackage the product, add a few more capabilities and reposition it. Repackaging is a bigger shift because you’re trying to go after a different market. Pharma companies are very good at that — they'll re-patent, add a few more capabilities, and then what was once an antidepressant now becomes a weight loss drug. You also have to know what is driving that pivot. Is it market demand? Is there a gap in the market for something new? Is it timing, because you want to be first to market, or is it a competitive response? It could be what I call an influence shift, which happens when you intentionally change the direction of the product based on the input of a big customer. Another potential reason is that an investor is making you pivot because they see your startup from a different vantage point than you as the founder. So understand why you're pivoting, but also be ready to pivot away from your initial pivot if it's not working out — don't get married to your strategy. Strategy changes, so be nimble about it as you go, and understand the shifts that are happening.

Is stability / uptime a concern for you with your cloud provider?  Thinking back to AWS' major outage in 2017, shouldn't we be past these issues? https://www.zdnet.com/article/ibm-cloud-outage-downs-customer-websites-globally/?ftag=TRE-03-10aaa6b&bhid=29349190877791638188562104926226&mid=12873514&cid=2259891406

Top Answer: It should be a concern.    No Hyperscaler is immune,  and we're not past these issues. AWS confirmed on 12-07-2021 "it was experiencing issues in the US-East-1 Region" that took down business and consumer services.  Many companies have already adopted a Multicloud strategy.  Moreover, it makes sense to use cloud service providers with complementary capabilities so that the business maintains access to best in class technologies.

At your organization, how much regression testing for new app features is done manually vs. how much is automated?

Top Answer: Hmmm, we do 100% automated except in a few places where it is not possible.  We are starting to deploy robot arms and so advice mobile testing capabilities to shrink those parts.  Still a little catch up work on a few legacy technologies.  We test too often for it to be manual.