Tech For Non Techies - Speaker Deck

Slide 1

Slide 1 text

Ahmad El-Alfy / 26 August 2023 Tech for Non-Techies Exploring the Software Development Life Cycle, Methodologies, and Deliverables for Non-Technical Audiences

Slide 2

Slide 2 text

Hi • I work as the CTO of Robusta Technology Group. • Have around 8 years of experience in managing software development teams. • A signi fi cant part of my daily work involves communicating technical concepts to non-technical individuals (customers, designers, account managers … etc). • Started my software career as a self taught freelancer beside practicing medicine and surgery, then I decided to quit medicine permanently in 2011. • I am self proclaimed accessibility fanatic and I share considerable amount of bad puns and memes every day.

Slide 3

Slide 3 text

@ahmadalfy in/ahmadalfy

Slide 4

Slide 4 text

Why are we here? Almost all of us deal with technology on a daily basis. This world is driven by technology, and software lies at the heart of every digital product you encounter. A lot of business are built on top of that. They provide services that is delivered through software they own. You could be working in a company that does that or maybe you have an idea and you are interested in building your own company. In this session, we aim to demystify this world together. We will talk about how software is built, what type of functions or teams that can do it, the terminologies they use to communicate; so you can have meaningful conversations with those people without feeling that you’re left out.

Slide 5

Slide 5 text

Software Development Life Cycle

Slide 6

Slide 6 text

We want you to build as a skyscraper

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

The steps you need to build anything • Conceptualize and verify Idea • Requirements Gathering • Design and Planning • Construction • Testing and Quality assurance • Opening and Celebration 🎉 • Maintenance and Update • Conceptualize and verify Idea • Requirements Gathering • Design and Planning • Development • Testing and Quality assurance • Deployment and Release 😭 • Maintenance and Update

Slide 9

Slide 9 text

Requirements Gathering This is usually carried out by the di ff erent stakeholders involved. A stakeholder is anyone invested in the project. We could have external like the client or internal like project manager, designer, testers developers … etc.

Slide 10

Slide 10 text

Project Manager The project manager is responsible for overseeing the entire software development process. They coordinate and communicate with the team, stakeholders, and clients. Their role involves planning, organizing, setting deadlines, managing resources, and ensuring that the project is delivered successfully within budget and on time. Any Updates

Slide 11

Slide 11 text

Product Owner The Product Owner represents the interests of the stakeholders and acts as the bridge between the development team and the clients or end-users. They are responsible for defining and prioritizing the product backlog, making decisions on features and functionalities, and ensuring that the software aligns with the overall product vision.

Slide 12

Slide 12 text

Designer Designers are responsible for creating the visual and experiential aspects of the software. They work on user interface (UI) and user experience (UX) design, focusing on making the software intuitive, visually appealing, and user-friendly. Designers collaborate with developers to translate design concepts into functional interfaces.

Slide 13

Slide 13 text

Developers Developers are responsible for writing the code that brings the software to life. They implement the functionality, features, and logic based on the requirements and design specifications. They collaborate with designers, testers, and other team members throughout the development process.

Slide 14

Slide 14 text

Testers Testers, also known as quality assurance (QA) or software testers, play a crucial role in ensuring the software's quality. They create and execute test cases to identify bugs, errors, and vulnerabilities in the software. Testers work closely with developers to resolve issues and ensure the software meets the desired standards.

Slide 15

Slide 15 text

Design and Planning

Slide 16

Slide 16 text

Designers: Mockups and Wireframes

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Developers

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Product Owners

Slide 26

Slide 26 text

User Story

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

Development

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

Slide 33

Slide 33 text

SCRUM Roles   Product Owner, Scrum Master, and Development Team Events   Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective Artifacts   Product Backlog, Sprint Backlog, and Increment

Slide 34

Slide 34 text

Sprint planning

Slide 35

Slide 35 text

How does it go • Product owner starts by prioritizing the stories the team will be working on. • Developers verify the estimates added to the stories. • Developers align together and discuss any intersections and seek clarifications and answers to any ambiguous parts. • Sprint stories moved from the backlog to the sprint backlog and assigned to the corresponding developers. • Team commits to delivering these stories.

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

Fibonacci numbers Fibonacci numbers are often used to represent the relative difficulty or complexity of user stories or tasks during estimation. The Fibonacci sequence is a series of numbers where each number is the sum of the two preceding numbers: 0, 1, 1, 2, 3, 5, 8, 13, 21, and so on. It helps teams focus on relative sizing rather than absolute values, reducing the tendency to overestimate or underestimate tasks. It encourages discussions among team members during estimation, leading to a shared understanding of the work and fostering collaboration and alignment.

Slide 38

Slide 38 text

Daily Scrum

Slide 39

Slide 39 text

JIRA

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

Sprint Review

Slide 42

Slide 42 text

Sprint Retrospective

Slide 43

Slide 43 text

Next Sprint

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

Let’s take a closer look at the development team

Slide 46

Slide 46 text

Participate in Scrum Activities Write Code Review Code Fix bugs Ship features Create Artifact Specializations • Front-end Developer • Back-end Developer • Full-stack Developer • Mobile App Developer • DevOps Engineer • Architect • Data Scientist

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

No content

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

How do all these people work together?

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

Is this the only way?

Slide 58

Slide 58 text

Low-code platforms Low-code systems are development platforms that enable the creation of software applications with minimal hand-coding, using visual interfaces and declarative approaches These platforms can help with rapid application development and increase developers productivity. They are characterized by being easy to use, having great integration capabilities and allowing collaboration between di ff erent team members. By leveraging low-code systems, organizations can accelerate application development, and drive innovation, ultimately delivering software solutions more e ffi ciently and e ff ectively.