This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
We have explained how best to use JIRA (JIRA guide) and what should be taken care of in the “Planning and Initiation” phase of a project and “Execution” phase of the project with Scrum framework.
This document provides an overview of an Agile (Scrum) training covering core concepts like eliminating waste, amplifying learning, and deciding late. It discusses Scrum mechanics like user stories, estimating story points, and sprint ceremonies. It also covers broader Scrum concepts like releases, Scrum of Scrums, and accepting change. The training draws on the presenter's experience from multiple companies that transitioned to Agile and books on successful Agile implementation.
Introduction to agile and Scrum.
Using Vera Peeters and Pascal Van Cauwenberghe's XP game as a basis, we have adapted it to explain and demonstrate agile and Scrum. The second half of the presentation is largely repetitive because it is used at each stage in the game.
The document provides an overview of the Scrum process. Some key points:
- Scrum is an agile process that focuses on delivering high business value in short iterations through inspecting working software every 2-4 weeks. The business prioritizes features.
- Roles include the Product Owner who manages the product backlog, Scrum Master who facilitates the process, and cross-functional team.
- Artifacts include the product backlog, sprint log/burndown chart, task board, and velocity/capacity metrics.
- Activities include sprint planning, daily stand-ups, sprint demo/review, and retrospective meetings. Definitions of ready, done are established along with team values.
The document summarizes the author's experience transitioning from a traditional waterfall development process to working on an agile software engineering team. Some key points:
- She has worked as a technical writer for 25 years and facilitated her team's switch to agile 10 years ago.
- Agile utilizes short 2-4 week cycles called sprints, daily standups, and demos instead of long documentation deliverables.
- On the agile team, she takes on various roles like Scrum Master and helps with testing and code changes in addition to documentation.
- The author believes agile has increased her job satisfaction, career success through promotions, and involvement in decision making. However, it can be developer-centric
This was some thoughts for maturing our Agile SDLC with some specific notes on how to improve JIRA workflows. This was a discussion slide deck; it's very wordy
We have explained how best to use JIRA (JIRA guide) and what should be taken care of in the “Planning and Initiation” phase of a project and “Execution” phase of the project with Scrum framework.
This document provides an overview of an Agile (Scrum) training covering core concepts like eliminating waste, amplifying learning, and deciding late. It discusses Scrum mechanics like user stories, estimating story points, and sprint ceremonies. It also covers broader Scrum concepts like releases, Scrum of Scrums, and accepting change. The training draws on the presenter's experience from multiple companies that transitioned to Agile and books on successful Agile implementation.
Introduction to agile and Scrum.
Using Vera Peeters and Pascal Van Cauwenberghe's XP game as a basis, we have adapted it to explain and demonstrate agile and Scrum. The second half of the presentation is largely repetitive because it is used at each stage in the game.
The document provides an overview of the Scrum process. Some key points:
- Scrum is an agile process that focuses on delivering high business value in short iterations through inspecting working software every 2-4 weeks. The business prioritizes features.
- Roles include the Product Owner who manages the product backlog, Scrum Master who facilitates the process, and cross-functional team.
- Artifacts include the product backlog, sprint log/burndown chart, task board, and velocity/capacity metrics.
- Activities include sprint planning, daily stand-ups, sprint demo/review, and retrospective meetings. Definitions of ready, done are established along with team values.
The document summarizes the author's experience transitioning from a traditional waterfall development process to working on an agile software engineering team. Some key points:
- She has worked as a technical writer for 25 years and facilitated her team's switch to agile 10 years ago.
- Agile utilizes short 2-4 week cycles called sprints, daily standups, and demos instead of long documentation deliverables.
- On the agile team, she takes on various roles like Scrum Master and helps with testing and code changes in addition to documentation.
- The author believes agile has increased her job satisfaction, career success through promotions, and involvement in decision making. However, it can be developer-centric
Bruce Nix provides an introduction to agile and Scrum. He summarizes his experience working with various companies to implement agile and Scrum practices. He then discusses some of the key principles of agile, including self-organizing teams, frequent delivery of working software, and responding to change. The rest of the document delves into the specifics of Scrum, including roles, ceremonies like the daily standup and sprint planning, and challenges with adoption.
Pactical case of Atlassian Tools implementation Yuriy Kudin
This document summarizes a presentation about choosing project management tools. It discusses the client's initial request for help with their tools, an audit of the client's current process, and a proposed solution using Jira and Confluence. The proposed solution includes restructuring the organization and product hierarchies, formalizing workflows for epics, stories, and tasks, and setting up boards and reporting. It acknowledges some challenges with scaling Jira and considers VersionOne as an alternative. In the end, it recommends choosing tools to match the project processes and needs.
This slides-share describes best practices to implement Jira in software development organizations who practice Agile.
The focus is on simple implementation based on Jira core and portfolio to achieve high ROI
This document provides an introduction to Kanban, an agile methodology that focuses on visualizing and limiting work-in-progress to continuously improve workflow. It defines Kanban and how it was inspired by lean manufacturing practices. The core practices of Kanban are outlined, including defining and visualizing the workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to suggest improvement. An example Kanban board is demonstrated. Finally, the document discusses how to build a Kanban process by defining queues and work items, setting work-in-progress limits, establishing delivery cadence, and continually improving the process through Kaizen.
Introduction to JIRA & Agile Project ManagementDan Chuparkoff
This document provides an introduction to using JIRA for agile project management. It discusses key concepts like defining tasks, estimating task effort in story points, and using JIRA's agile tools like boards and burndowns. Screenshots show how to create and manage tasks in JIRA's different modes for Scrum and Kanban workflows.
Using Atlassian with Agile project management: JIRA, GreenHopper and moreAtlassian
JIRA + Greenhopper might be Agile's best kept secret. Whether you're exploring Agile, already a blackbelt or just looking for a slick interface to JIRA, this session will help you understand how to use JIRA as your agile workbench.
Customer Speakers: Jim Morris of Buzzillions, Jean-Christophe Huet of Greenpepper
Key Takeaways:
* GreenHopper plugin overview
* How to use JIRA for agile project management
This document summarizes a presentation by Gerard Beckerleg on using Scrum with Team Foundation Server (TFS) 2012. The presentation covers Agile and Scrum theory, walks through a sample project using manual Scrum processes, and demonstrates how to use TFS 2012 and its Scrum template. It discusses the history of Scrum at SSW, an overview of Scrum roles, artifacts, and events, and how to implement the core Scrum processes like sprint planning, daily standups, reviews, and retrospectives.
This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.
A New Behavior-Driven Development Method, Specification by Example
Easy to expand more examples by more parameter values by sheet
End user can’t reject Excel, they like to use Excel to express what they need precisely
This document provides guidance on facilitating effective Product Backlog Refinement sessions. It discusses that PBR is a process where the Scrum team reviews and revises product backlog items to provide more detail and clarity. It recommends having all Scrum team members participate. An agenda, required participants, time-boxing, environment setup, warmup activities, and techniques for refinement like prioritization matrices and estimation are discussed to help plan successful PBR sessions. Minutes and follow-up tasks are also important elements covered.
This document provides an overview of agile marketing and the Scrum framework. It discusses agile values and principles, including prioritizing customer satisfaction, welcoming change, and frequent delivery of working software. It then outlines the Scrum process, including sprints, roles of product owner, Scrum master and team. Key Scrum ceremonies are sprint planning, daily scrums, sprint reviews and retrospectives. Artifacts include the marketing backlog, sprint backlog and burn down charts.
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
The document provides instructions for using key features of an agile project management tool called Version One. It describes how to create projects, assign team members, schedule sprints and releases, track work during sprints using a taskboard and storyboard, and conduct sprint reviews and retrospectives. The steps covered include creating projects and member accounts, assigning roles, scheduling releases and sprints, tracking work completion and moving items between sprints.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
The document discusses implementing Kanban for services teams. It describes the typical push model used by many services teams and its problems. It then suggests adopting a pull model using Kanban with a Kanban board to visualize workflow. Key aspects of Kanban discussed include limiting work in progress, continuous flow, and using it to identify impediments. The document also discusses combining Kanban with aspects of Scrum and emphasizing continuous improvement.
Rational Team Concert is a tool that allows development teams to plan projects, track work items and code changes, and collaborate in one integrated environment. It provides source control, work item tracking, build management, and dashboards. This helps teams work more efficiently through features like real-time planning, traceability between code and work items, continuous integration, and visibility into project status. The document discusses how Rational Team Concert supports agile project management practices like iteration planning, tracking progress through burndowns, and parallel development with source code management.
Ravi Tadwalkar as SM/DevOps/management/CoachRavi Tadwalkar
The document discusses the roles and responsibilities of a Scrum Master, DevOps Manager, and DevOps Coach. It provides examples of how DevOps adoption improved deployment processes at companies like PayPal and Western Digital. Specifically, implementing continuous integration/deployment and embedding release engineers into agile teams reduced PayPal's deployment time from 6 weeks to 9 days. For Western Digital, using a common code repository improved their firmware integration from twice a week to on-demand. The document also outlines the author's experience over 20 years in software development, management, coaching, and DevOps roles.
A step-by-step checklist for how to manage your agile sprint. This presentation will point you to the right direction and mentions all the keywords you need to know when approaching the agile methodology.
Lean Manufacturing's Influence on Agile Stephen Forte
Lean manufacturing principles influenced the development of agile software development methodologies. Extremem Programming (XP), an early agile methodology, was influenced by lean principles focusing on eliminating waste. Scrum, the most popular current methodology, was directly inspired by lean manufacturing processes. Kanban, an emerging agile methodology, focuses on limiting work in progress like lean's just-in-time approach. Overall, lean thinking provides an effective framework for agile practices by emphasizing value creation and waste reduction.
The document provides an overview of Agile Scrum methodology. It describes the key roles of Product Owner, Scrum Master, and Team. It explains the main Scrum processes of Release Planning, Sprint Planning, Daily Scrum, Sprint, Sprint Review, and Sprint Retrospective. It outlines the activities involved in each process and how they contribute to delivering working software in an iterative manner through inspection and adaptation.
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
Orangescrum Enterprise edition is widely popular as it offers end to end project management capabilities across industries. Its plugins can be seamlessly installed and offer you perpetual license for unlimited users.
Bruce Nix provides an introduction to agile and Scrum. He summarizes his experience working with various companies to implement agile and Scrum practices. He then discusses some of the key principles of agile, including self-organizing teams, frequent delivery of working software, and responding to change. The rest of the document delves into the specifics of Scrum, including roles, ceremonies like the daily standup and sprint planning, and challenges with adoption.
Pactical case of Atlassian Tools implementation Yuriy Kudin
This document summarizes a presentation about choosing project management tools. It discusses the client's initial request for help with their tools, an audit of the client's current process, and a proposed solution using Jira and Confluence. The proposed solution includes restructuring the organization and product hierarchies, formalizing workflows for epics, stories, and tasks, and setting up boards and reporting. It acknowledges some challenges with scaling Jira and considers VersionOne as an alternative. In the end, it recommends choosing tools to match the project processes and needs.
This slides-share describes best practices to implement Jira in software development organizations who practice Agile.
The focus is on simple implementation based on Jira core and portfolio to achieve high ROI
This document provides an introduction to Kanban, an agile methodology that focuses on visualizing and limiting work-in-progress to continuously improve workflow. It defines Kanban and how it was inspired by lean manufacturing practices. The core practices of Kanban are outlined, including defining and visualizing the workflow, limiting work-in-progress, measuring and managing flow, making process policies explicit, and using models to suggest improvement. An example Kanban board is demonstrated. Finally, the document discusses how to build a Kanban process by defining queues and work items, setting work-in-progress limits, establishing delivery cadence, and continually improving the process through Kaizen.
Introduction to JIRA & Agile Project ManagementDan Chuparkoff
This document provides an introduction to using JIRA for agile project management. It discusses key concepts like defining tasks, estimating task effort in story points, and using JIRA's agile tools like boards and burndowns. Screenshots show how to create and manage tasks in JIRA's different modes for Scrum and Kanban workflows.
Using Atlassian with Agile project management: JIRA, GreenHopper and moreAtlassian
JIRA + Greenhopper might be Agile's best kept secret. Whether you're exploring Agile, already a blackbelt or just looking for a slick interface to JIRA, this session will help you understand how to use JIRA as your agile workbench.
Customer Speakers: Jim Morris of Buzzillions, Jean-Christophe Huet of Greenpepper
Key Takeaways:
* GreenHopper plugin overview
* How to use JIRA for agile project management
This document summarizes a presentation by Gerard Beckerleg on using Scrum with Team Foundation Server (TFS) 2012. The presentation covers Agile and Scrum theory, walks through a sample project using manual Scrum processes, and demonstrates how to use TFS 2012 and its Scrum template. It discusses the history of Scrum at SSW, an overview of Scrum roles, artifacts, and events, and how to implement the core Scrum processes like sprint planning, daily standups, reviews, and retrospectives.
This presentation gives you a detailed look at what is in the out of the box templates available in TFS 2013, how they differ, and how that affects some of the ALM tooling.
A New Behavior-Driven Development Method, Specification by Example
Easy to expand more examples by more parameter values by sheet
End user can’t reject Excel, they like to use Excel to express what they need precisely
This document provides guidance on facilitating effective Product Backlog Refinement sessions. It discusses that PBR is a process where the Scrum team reviews and revises product backlog items to provide more detail and clarity. It recommends having all Scrum team members participate. An agenda, required participants, time-boxing, environment setup, warmup activities, and techniques for refinement like prioritization matrices and estimation are discussed to help plan successful PBR sessions. Minutes and follow-up tasks are also important elements covered.
This document provides an overview of agile marketing and the Scrum framework. It discusses agile values and principles, including prioritizing customer satisfaction, welcoming change, and frequent delivery of working software. It then outlines the Scrum process, including sprints, roles of product owner, Scrum master and team. Key Scrum ceremonies are sprint planning, daily scrums, sprint reviews and retrospectives. Artifacts include the marketing backlog, sprint backlog and burn down charts.
The document provides an overview of Scrum basics and components. It introduces Scrum as an Agile framework and discusses its core elements - events like sprints, planning and reviews; roles like product owner and scrum master; and artifacts like product backlog and sprint backlog. It also covers related concepts like capacity, velocity and how Scrum compares to Agile approaches. The document concludes by suggesting resources to learn more about Scrum and offers coaching for teams to understand how to apply Scrum.
The document provides instructions for using key features of an agile project management tool called Version One. It describes how to create projects, assign team members, schedule sprints and releases, track work during sprints using a taskboard and storyboard, and conduct sprint reviews and retrospectives. The steps covered include creating projects and member accounts, assigning roles, scheduling releases and sprints, tracking work completion and moving items between sprints.
For numerous large enterprises, the alignment of hardware and software processes is critical to managing an Agile environment. Agile Hardware implementations can be put in place by using the same framework as our typical Agile Software Development transformations. Start off with assessing the organization’s current state, then move to planning and preparing by and putting together a transition backlog, start execution with training and coaching, spread the cultural shift with change management and maintain and scale the transformation.
The document discusses implementing Kanban for services teams. It describes the typical push model used by many services teams and its problems. It then suggests adopting a pull model using Kanban with a Kanban board to visualize workflow. Key aspects of Kanban discussed include limiting work in progress, continuous flow, and using it to identify impediments. The document also discusses combining Kanban with aspects of Scrum and emphasizing continuous improvement.
Rational Team Concert is a tool that allows development teams to plan projects, track work items and code changes, and collaborate in one integrated environment. It provides source control, work item tracking, build management, and dashboards. This helps teams work more efficiently through features like real-time planning, traceability between code and work items, continuous integration, and visibility into project status. The document discusses how Rational Team Concert supports agile project management practices like iteration planning, tracking progress through burndowns, and parallel development with source code management.
Ravi Tadwalkar as SM/DevOps/management/CoachRavi Tadwalkar
The document discusses the roles and responsibilities of a Scrum Master, DevOps Manager, and DevOps Coach. It provides examples of how DevOps adoption improved deployment processes at companies like PayPal and Western Digital. Specifically, implementing continuous integration/deployment and embedding release engineers into agile teams reduced PayPal's deployment time from 6 weeks to 9 days. For Western Digital, using a common code repository improved their firmware integration from twice a week to on-demand. The document also outlines the author's experience over 20 years in software development, management, coaching, and DevOps roles.
A step-by-step checklist for how to manage your agile sprint. This presentation will point you to the right direction and mentions all the keywords you need to know when approaching the agile methodology.
Lean Manufacturing's Influence on Agile Stephen Forte
Lean manufacturing principles influenced the development of agile software development methodologies. Extremem Programming (XP), an early agile methodology, was influenced by lean principles focusing on eliminating waste. Scrum, the most popular current methodology, was directly inspired by lean manufacturing processes. Kanban, an emerging agile methodology, focuses on limiting work in progress like lean's just-in-time approach. Overall, lean thinking provides an effective framework for agile practices by emphasizing value creation and waste reduction.
The document provides an overview of Agile Scrum methodology. It describes the key roles of Product Owner, Scrum Master, and Team. It explains the main Scrum processes of Release Planning, Sprint Planning, Daily Scrum, Sprint, Sprint Review, and Sprint Retrospective. It outlines the activities involved in each process and how they contribute to delivering working software in an iterative manner through inspection and adaptation.
This document provides an introduction to Agile project management frameworks like Scrum and Kanban. It discusses the limitations of traditional waterfall project management and how Agile aims to address these issues through iterative development, collaboration, and flexibility. Key aspects of Scrum like roles, events, artifacts, estimation and user stories are explained. Kanban concepts such as visualizing workflow, limiting work in progress, and managing flow are also covered. The document recommends resources for learning more about Agile, Scrum, Kanban and hybrid approaches.
Orangescrum Enterprise edition is widely popular as it offers end to end project management capabilities across industries. Its plugins can be seamlessly installed and offer you perpetual license for unlimited users.
This document discusses Agile Project Management with Azure DevOps. It describes Azure DevOps as providing source control, build/release, Agile planning, testing, dashboards, and wikis. Traceability, automation of processes, and visibility are presented as pillars of traditional application lifecycle management. Work items are used in Azure DevOps to track requirements, bugs, tasks, and more, with customizable fields and states. Work items can be nested to show hierarchies.
Simple and Effective TMS helps to manage and track task, business projects or processes.
A Complete Solution for
Project Planning
Strategy Implementation
Document Sharing
EOD,EOW,EOM Activity
Reminders & Accountability
A brief reflection on the Waterfall approach, review the Scrum elements and artifacts, and their purpose. Demonstrate Agile Scrum by providing real-world examples that delivered successful measurable outcomes to the business.
This presentation describes the basics of Agile methodologies and how it is differed from Waterfall. Then continues with the most famous Agile approach: Scrum
Making the Transition to Agile: what we did, what worked, and what we learnedAri Davidow
In 2008 the Jewish Women's Archive (JWA) tried Agile Software development as a tool to select the necessary User Stories and develop a working, lightweight interface to the Fedora Commons digital archive. The project succeeded. That software was later taken by the developer and open sourced as the "hydra" project.
The document outlines the user experience design process at iSL, beginning with kickoff and discovery activities to understand goals and identify problems. It then defines key terms like user experience, information architecture, and visual design. The process involves content audits, sitemaps, user flows, and iterative wireframes to define functionality before design and development begin. Reviews ensure alignment across teams. The outcomes aim to guide layouts, prevent scope creep, identify content gaps, and help clients understand functionality for approval.
Agile planning with Rational Team Concert (RTC) workshop provides tip for agile team to successfully use RTC to support for the three innermost levels of Mike Cohn's planning onion: product, release and sprint / iteration planning. RTC also provides extensive support source code management and integration to CI build and automated release deployment tools such as UrbanCode Deploy
For more information see https://jazz.net/library/article/593
Details
Rational Team Concert (RTC) provides a lightweight tool to help project teams plan, executing and monitor agile, waterfall and scaled agile development projects (such as Scrum, Scrum of Scrums, Disciplined Agile Delivery - DAD, or Scaled Agile Framework - SAFe.
For agile projects / programs, RTC provides tools to create product, release and sprint backlogs for teams, to create individual plans for developers, and to track the progress during an iteration and to balance the work load of developers.
For waterfall projects / programs, RTC provides development teams with traditional project management capabilities such as work breakdown structures, schedule dependencies, constraints and Gantt charts.
User Centered Agile Development at NASA - One Groups Path to Better SoftwareBalanced Team
The group at NASA iteratively adopted agile practices over two years to improve their software development process. They started with six month development cycles and shortened this to six weeks and then three weeks. This allowed for more frequent customer feedback and prioritization of work. Daily builds and testing ensured progress was always visible. Their measure of success became working code delivered in frequent iterations rather than presentations or documentation.
User centered agile dev balanced team 2013Jay Trimble
The group at NASA iteratively adopted agile practices over two years to improve their software development process. They started with six month development cycles and shortened this to six weeks and then three weeks. This allowed for more frequent customer feedback and prioritization of work. Daily builds and testing ensured progress was always visible. Their measure of success became working code delivered in frequent iterations rather than presentations or documentation.
A 1 Day training that shows you all you need to know about Scrum, the afternoon contains a practical part where we perform several sprints using Lego as our means of production
Chris OBrien - Azure DevOps for managing workChris O'Brien
A presentation I gave at ESPC 2019 (the European SharePoint, Office 365 and Azure Conference) about Azure DevOps for managing both development and support work. The focus is on Azure DevOps boards and task management, but covers some CI/CD aspects too.
This document discusses Johnson Controls' deployment of Microsoft Project Server 2010 and SharkPro Projects for project management of their Global Finance transformation. They selected this system over their existing Clarity system to enable global visibility and scalability for over 300 projects. With help from SharkPro, they were able to simplify key processes like plan-building, scorekeeping, and weekly updates. This resulted in significant time savings and improved engagement through a focus on deliverables, accountability, and a single schedule performance metric. The simplified approach paid off for their project management office processes.
With an agency focus on IoT/M2M and other technology-based clients, it's in ThreeTwelve's DNA to elevate people over process by adapting Agile methodology to an agency setting. Here's an introduction to how and why we do what we do, the way we do.
Working with IoT/M2M and other technology-driven businesses, it's only natural that elevating people over process by adapting Agile methodologies with our clients is in our DNA. Here's a brief overview of how and why we do things the way we do.
The document outlines the key aspects of Scrum, an iterative framework for managing complex projects. Scrum utilizes short development cycles called sprints, daily stand-up meetings, and emphasizes self-organizing cross-functional teams to frequently deliver working software and adapt to changes through its event-driven process of sprints, planning meetings, reviews, and retrospectives. The roles in Scrum include the Product Owner, the Development Team, and the Scrum Master.
Q-Track is an Enterprise Task Management solution which helps you to collaborate within organizations effectively and execute tasks on time and pro-actively. It helps managers to have track on delegated tasks and help their sub-ordinates to close them on exceptions. The solution has seamless integration with MS outlook and MS Projects.
The document discusses implementing Agile software development using JIRA and CI/CD. It describes key Agile methodologies like Scrum and Kanban and compares them. It then explains what JIRA is and how it can be used to manage an Agile software development workflow, including concepts like projects, issues, tasks and sprints. It also covers setting up a CI/CD pipeline using Jenkins and git to enable continuous integration and delivery.
Similar to Jira workflow for documentation issue types agile edition (20)
The document proposes a cost reduction plan for an AWS environment with current annual spend of $490k. It identifies five key areas for cost savings: 1) Implementing autoscaling for environments to better match usage and reduce overprovisioning, estimated at $96k in savings. 2) Managing development/production instances to turn off non-peak periods, estimated $84k savings. 3) Using spot instances for machine learning training for $48k savings. 4) Switching model builds to serverless technologies for $6k savings. 5) Controlling S3 storage and implementing data lifecycles for $18k savings. The plan estimates a total of $252k in annual savings, over 50% reduction in AWS
Response on Proposal for Converting to a Gated CommunityMichael J Geiser
This is a response to the request from the HOA Board for proposal to Convert Bayside at Bethany Lakes into a Gated Community in reaction to a string burglaries in 2013
There have been a number of articles and other content appearing in SI that have not met the standards and guidelines the Skeptical communities expects
1967 lincoln continental convertible restoration v4Michael J Geiser
This document provides updates on a 1967 Lincoln Continental convertible restoration project. It details plans to use a totaled 2016 Mustang GT as a donor vehicle for the motor, transmission, radio, HVAC controls, steering wheel, and other interior components. The target is to complete the exterior restoration to original 1960s specifications while incorporating modern interior components from the 2016 Mustang for the seats, center console, and rear speakers.
Agile Progress Tracking and Code Complete Date EstimationMichael J Geiser
Here are two tools that I found to be very effective in predicting Code Complete dates and the effect of scope changes and also tracking progress against a Development Plan over time
Release Planning is a Pain Point in many Agile shops. This is an outline of a process that has worked very well for me over time. I hope you find it useful also.
I’ve been keeping a collection of Linux commands that are particularly useful; some are from websites I’ve visited, others from experience
I hope you find these are useful as I have. I’ll periodically add to the list, so check back occasionally.
Introduction to the WSO2 Identity Server &Contributing to an OS ProjectMichael J Geiser
This is an overview of the WSO2 Identity Server and a customization we built that will be contributed back into the product. There is also some additional content on Coding Standards and being an LDAP an Directory Server hater
This document outlines a network architecture with firewalls separating the internet, DMZ, and internal segments. An F5 load balancer distributes traffic for my-api.mydomain.com across two instances of MyService running on dc1-myservice.myinternaldomain.net and dc2-myservice.myinternaldomain.net.
Using JIRA to Manage Project Management Risks and Issues Michael J Geiser
The document discusses managing project risks and issues using JIRA's risk management workflow. It recommends using JIRA over other project management software for risk tracking because it has wider company adoption, visibility, and the ability to assign risks to any JIRA user to track progress. The JIRA risk management workflow standardizes the risk management process, ties risks to specific work, and creates an organizational knowledge base of risks across projects for transparency.
The document describes an approvals workflow that involves multiple steps:
1. Issues such as change requests, improvements, and feature requests are created.
2. The requests go through stages of being opened, documented, analyzed for impact and risk, and reviewed by committees.
3. The workflow provides advantages like a standardized process, centralized knowledge capture, and easy tracking of all approvals linked to each issue.
Ready to Unlock the Power of Blockchain!Toptal Tech
Imagine a world where data flows freely, yet remains secure. A world where trust is built into the fabric of every transaction. This is the promise of blockchain, a revolutionary technology poised to reshape our digital landscape.
Toptal Tech is at the forefront of this innovation, connecting you with the brightest minds in blockchain development. Together, we can unlock the potential of this transformative technology, building a future of transparency, security, and endless possibilities.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
3. 3
JIRA Workflow for Documentation Issue Types (Agile Projects)
This is a redraw of the original diagram you provide adding the “Approved” status we discussed and
with all the transitions drawn in (I added the “Assigned” status over what we discussed yesterday)
• When you add in all the transitions, it gets more complex looking but it’s almost the same process.
– There are only a few transitions from any specific step and the Transition names are designed to make the
choices clear and self-documenting.
• “Available”, “In Progress” and “Assigned” Statuses: Implementing this way allows you to
– Plan Work: Instantly gauge Capacity (“In Progress”) against Demand (“Available” and “Assigned”)
– Limit Work in Progress (“WIP”): Tech Writers should not be working on too many things concurrently, overloading
increases defect rates and increases risk to delivery schedule
– Tech Writers really only ever deal with Available & Assigned to get work, In Progress when working on
something and then In Review when they are finished
How work gets picked up or assigned:
• A manager or writer can assign “Available” work based on prior experience or other reason.
• “Available” work can be picked up as a writer has capacity
• If priorities change, the work can be returned to “Available” for someone else to pickup or the writer
can return it to “Assigned” to save it for themselves to get back to later.
• You can use an Agile “card wall” for Writers to pick and put Agile on your resume!
• You can easily track the status of all work by assignee to balance work and gauge productivity
• With a small amount of work when defining the workflow, we can collect data to get info like “Days
in Development”
4. 4
JIRA Workflow for Documentation Issue Types (Agile Projects)
Tracking Progress
• You can easily track the status of all work by assignee to balance work and gauge productivity
• With a small amount of work when defining the workflow, we can collect data to get info like “Days
in Development”