Lunr Management Model and Employee Handbook
  • 👋Welcome to LUNR!
  • About us
    • 🚀Vision, Mission & Focus
      • Vision
      • Mission
      • Pillars
  • How We Make Decisions
    • 🚀Strategy
      • Context, not control
      • Strategic management
      • Culture code
    • 🏹Leadership
      • Managers
      • Tech leads
      • Traits of leadership
      • Leaders Performance
    • 👭Team management
      • Team Structure Designed for Success
      • Embracing Effective Ceremonies
      • Strategic Sessions: Empowering Innovation
  • How we build processes and a great product
    • ⚙️Operations and roles
      • How We Navigate Growth and Complexity
      • Our Responsibility Assignment Matrixes: RACI & CODE-KS
    • 📚Knowledge management
      • Knowledge Categories
      • Knowledge Accountability Index
      • Confluence
      • Learning day
      • Company Knowledge Centricity Level
      • Realms
    • 👨‍💻Engineering culture
      • Engineering culture
      • Team culture
      • Engineering Process and Roles
      • Team Events and Processes
        • Scrum Events
        • Ongoing Meetings
        • Concepts
  • How we ensure people’s growth
    • 📈Performance
      • Paths
        • Individual Contributors Path
          • Individual Contributors Levels - Software Engineering
          • Individual Contributors Steps
        • Management Path
          • Level 1 - Our Pace setters
          • Level 2 - Our Coaches
          • Level 3 – Our visionaries and servant leaders
          • Level 4 – Our transformational leaders
          • Key concepts
      • Performance evaluation
      • 360 Evaluation Matrix
      • K-POC
      • CAP
      • Management Model Golden Rules
    • 💰Compensation
      • IC Frameworks
        • 👨‍💻Android Development
        • 📱Android OS Development
        • 🔐Assets security
        • 👨‍💼Business Development
        • 📧Digital marketing
        • 💻Front-end web development
        • ⌨️Full Stack Web Development
        • 🏢Facility cleaning
        • 🔑Information security
        • ↗️Marketing automation
        • 🐞QA automation
        • 👾Quality assurance
        • 🧍Recruiting Operations
        • 📖Technical Training
        • 🤦Technical recruitment
        • 🤖WordPress Developers
        • 👩‍🎨UX/UI
      • MGT Frameworks
        • 👨‍💻Application support management
        • ➗Accounting&Finance Management
        • 👯HR Operations Management
        • 🔒Information Security Management
        • 📧Marketing Management
        • 📞NOC&Support management
        • 🚵Operations management (logistics)
        • 🤦‍♀️Operations management (administration)
        • 🖥️Product owner
        • 🔩Product Engineering Management
        • 🤝Product Marketing Management
        • 👨‍💼Project Management (Business)
        • 👨‍💻Project Management (Software)
        • 🛒Sales Management
        • 📳Software Engineering Management
        • 🌟Strategic Business Development Management
        • 💟Strategic Human Resources Management
        • 🚟Supply Chain Management
        • 👌Technical Account Management
        • ☎️Technical Support Management
        • 📜Technical Training Management
    • 🌟Empowering Growth through Transparent Management: Your Path to Success
  • Policies
    • 🎹Internal rules
      • Employee Probationary Period
      • Employee Code of Conduct
      • Physical Access Control
      • Cybersecurity and digital devices
        • Internet usage
        • Cellphone
        • Corporate e-mail
        • Social media
        • Conflict of interest
        • Workplace measures
        • Employee relations
        • Solicitation and Distribution
      • Substance Abuse and Drug Testing Policy
      • Employee Attendance and Working Hours Policy
      • Shiftwork Policy
      • Overtime policy
      • Employee Time Off Policy
      • Remote office policy
      • Smoke-free office policy
      • Employee Referral Program Policy
      • Moonlighting Policy
      • Anti-discrimination Policy
      • Violence In The Workplace Policy
      • Workplace Harassment Policy
      • Source Code Policy
      • Data Protection and Privacy Policy
      • Employee Confidentiality Policy
      • Business Trips Policy Policy
      • Company Equipment Policy
      • Event Participation Policy
      • Training Benefit Policy
      • Termination of Employment Policy
      • Disciplinary Action Policy
      • Corrective Action Plan (CAP) Policy
    • 💵Salaries
    • 📖LUNR knowledge
    • 🧙Sources
    • 📑Glossary
  • ©️License
Powered by GitBook
On this page
  • Product Refinement
  • Technical Debt session
  • Problem Review and Retrospective
  1. How we build processes and a great product
  2. Engineering culture
  3. Team Events and Processes

Ongoing Meetings

Product Refinement

Product Backlog refinement is an ongoing process in which the Product Owner and the Development Department collaborates on the details of Product Backlog items. During the meeting, items are reviewed and revised. The Scrum Team decides how and when refinement is held. Refinement usually consumes no more than 10% of the capacity of the Development Department. However, Product Backlog items can be updated at any time by the Product Owner. The goal of the refinement process is to have a clear understanding of every item so it can reasonably be "Done" within the Sprint time-box.

Technical Debt session

A technical Debt session is a process that brings value to product quality. Those meetings happen when needed and requested by the Development Department. Their scope is to discuss technical quality-related topics and create a plan for handling the technical debt. At the end of the session, the team should have a clear idea of what is to be done and how it would happen. The Development Department creates diagrams related to the desired solution or if the scope needs further investigation and time - the Product Owner creates a ticket for needed diagrams and documentation for the plan. The ticket has a responsible person and prioritization to enter in development ASAP.

Problem Review and Retrospective

This meeting happens after we have encountered critical obstacles. We see a continuous cycle of repeated mistakes or unproductive behavior. We discuss what happened and list all the events that caused the issue. We make improvement items that we can act on, related to process, communication, and collaboration. It is essential to keep the focus on the main goal: to find better ways for us to work together. We bring transparency for finalization on items through concepts which you will see in the next page.

PreviousScrum EventsNextConcepts

Last updated 11 months ago

👨‍💻