Luisa Pinto lrpinto

Use Case Scenarios for Software Engineers in Cross-Functional Teams

1. Giving Feedback on Product Requirements

Situation: The product team has provided feature requirements that are technically complex and could delay the project timeline.

Approach:

Feedback: “I see that the proposed features offer great value, but some of the requirements, like X and Y, might significantly extend the timeline.”
Suggest Adjustments: “Would it be possible to break these features down into phases? For example, we could deliver the core functionality first, then add additional features in a subsequent release.”
Align on Priorities: “By phasing it, we can ensure the highest impact features are delivered sooner without delaying the entire project.”

Effective Feedback for Stakeholders and Colleagues

Giving constructive feedback is essential for team growth and project alignment. This guide covers practical strategies for delivering feedback that respects professional boundaries, fosters positive relationships, and addresses emotional reactions constructively.

1. Setting the Stage for Feedback

For Stakeholders:

Contextualize the Feedback: Tie feedback directly to business goals or project outcomes. Frame it as part of the shared objective rather than personal critique.

Table: Stakeholder Descriptions for Technical Terms

This table that categorises various technical terms according to the audience (junior, mid-level, senior, CTO, VP Engineering, CEO, CMO, CFO, COO) and provides a brief script on how to describe each term to those stakeholders.

| Term | Junior | Mid-Level | Senior | CTO | VP Engineering | CEO | CMO | CFO | COO | |---------------|------------------------------------------|----------------------------------------|------------------------------------------|-------------------------------------------|----------------------------------------|------------------------------------------|-------------------------------------------|--------------

OpenShift CLI (oc) Cheat Sheet

Basic Commands

Login to OpenShift

oc login <server_url> --token=<your_token>

Prioritisation Frameworks Comparison in Product Management

Comparison table for the 5-Pillar, RICE, 3 Buckets, and MoSCoW prioritization frameworks, all in the context of product management:

Framework	When to Use	When Not to Use	Benefits	Cons
5-Pillar	Ideal for comprehensive product strategy evaluation and decision-making.	Less suited for quick, simple decisions or small-scale projects.	Offers a holistic view across Reach, Customer Impact, Business Impact, Validation, and Ease.	Can be complex and require significant cross-functional input and data analysis.
RICE	Best for quantifiable and data-driven decision-making.	Not ideal when impact is difficult to measure or quantify.	Provides a clear, quantifiable method to assess Reach, Impact, Confidence, and Effort.	May overlook qualitative aspects; relies on accurate and available data for scoring.
3 Buckets	Useful for initial sorting of features or ideas in

Here's a table outlining the capabilities and limitations of Figma, Jira, and Confluence. This comparison should give you a clear idea of what each tool is best suited for:

Feature/Capability	Figma	Jira	Confluence
User Interface Design	✅ Can create and prototype UI designs, including vector graphics and interactive elements.	❌ Not designed for UI creation.	❌ Not for UI design, but can embed designs from tools like Figma.
Project Management	❌ Limited project management features; mainly a design tool.	✅ Comprehensive project management capabilities, including issue tracking, agile boards, and project roadmaps.	❌ Not a project management tool, but integrates well with Jira for project documentation.
Collaboration & Feedback	✅ Real-time collaboration and feedback on designs, including commenting and version control.	✅ Collaboration through task assignments, comments, and workflow status updates.	✅ Excellent for c

Penguin Card Development Guide

Technology: Android

PenguinCard is a sample Android project that shows how to draw an occasion card for Android devices. The PenguinCard was built using just a few XML Android Components, such as RelativeLayout, ImageView and TextView. The coolest part is that you actually draw a Penguin!

This guide drives you through the development process for getting the PenguinCard done. It is really fun!

Sketching the PenguinCard

	//--------- App code ---------//

	const ADD_TODO = 'ADD_TODO'
	const REMOVE_TODO = 'REMOVE_TODO'
	const TOGGLE_TODO = 'TOGGLE_TODO'
	const ADD_GOAL = 'ADD_GOAL'
	const REMOVE_GOAL = 'REMOVE_GOAL'

	// Example taken from Expo - https://docs.expo.io/versions/latest/sdk/camera/
	// I have just added some comments
	// Try the Snack https://snack.expo.io/@techmummy/camera-example

	import React from 'react';
	import { Text, View, TouchableOpacity } from 'react-native';

	/* Import App and Camera Permissions */
	import * as Permissions from 'expo-permissions';
	import { Camera } from 'expo-camera';