Getting to Flow in Software Development (ASWEC 2014 Keynote)Gail Murphy
Humans are amazing at processing information. It is a good thing that they are because software development projects generate a tremendous amount of information of various forms from predominantly natural language documents like requirements to blended natural language and structured artifacts like issues to predominantly structured source and test code. For some time, the amount of information produced daily in a large software development has exceeded a human’s ability to process that information. Instead of producing tools that allow a software developer to focus on information pertinent to a task, too many tools have been built that focus solely on producing as much information as possible. In this talk, I will discuss interaction styles for tools that may bring us closer to keeping a developer in the flow of a task. By improving flow, we can enable developers to work smarter, work better and have more fun.
Project Estimation Presentation - Donte's 8th level of estimating level of ef...Promet Source
Johnnie Fox, Project Manager at Promet delivers this overview on web development project estimation, how to do it right and the pitfalls to watch out for.
Presented at Agile Prague (15th September 2014)
Video available at https://vimeo.com/107919080
Apparently, everyone knows about patterns. Except for the ones that don't. Which is basically all the people who've never come across patterns... plus most of the people who have.
Singleton is often treated as a must-know design pattern. Patterns are sometimes considered to be the basis of blueprint-driven architecture. Patterns are also seen as something you don't need to know any more because you've got frameworks, libraries and middleware by the download. Or that patterns are something you don't need to know because you're building on UML, legacy code or emergent design. There are all these misconceptions about patterns... and more.
In this talk, let's take an alternative tour of patterns, one that is based on improving the habitability of code, the expression of process and the habit of practice. Patterns are about communication, exploration, empiricism, reasoning, incremental development, sharing design and bridging rather than barricading different levels of expertise.
Getting to Flow in Software Development (ASWEC 2014 Keynote)Gail Murphy
Humans are amazing at processing information. It is a good thing that they are because software development projects generate a tremendous amount of information of various forms from predominantly natural language documents like requirements to blended natural language and structured artifacts like issues to predominantly structured source and test code. For some time, the amount of information produced daily in a large software development has exceeded a human’s ability to process that information. Instead of producing tools that allow a software developer to focus on information pertinent to a task, too many tools have been built that focus solely on producing as much information as possible. In this talk, I will discuss interaction styles for tools that may bring us closer to keeping a developer in the flow of a task. By improving flow, we can enable developers to work smarter, work better and have more fun.
Project Estimation Presentation - Donte's 8th level of estimating level of ef...Promet Source
Johnnie Fox, Project Manager at Promet delivers this overview on web development project estimation, how to do it right and the pitfalls to watch out for.
Presented at Agile Prague (15th September 2014)
Video available at https://vimeo.com/107919080
Apparently, everyone knows about patterns. Except for the ones that don't. Which is basically all the people who've never come across patterns... plus most of the people who have.
Singleton is often treated as a must-know design pattern. Patterns are sometimes considered to be the basis of blueprint-driven architecture. Patterns are also seen as something you don't need to know any more because you've got frameworks, libraries and middleware by the download. Or that patterns are something you don't need to know because you're building on UML, legacy code or emergent design. There are all these misconceptions about patterns... and more.
In this talk, let's take an alternative tour of patterns, one that is based on improving the habitability of code, the expression of process and the habit of practice. Patterns are about communication, exploration, empiricism, reasoning, incremental development, sharing design and bridging rather than barricading different levels of expertise.
How To Handle Exploding Complexity in Product DevelopmentPerforce
Was everything tested before the product shipped?
Were all requirements met?
Are you sure?
As product development explodes with complexity (and as requirements & tests evolve during development), many design teams struggle to answer these questions with confidence.
Knowledge gaps in product development add risk. Never good—especially in regulated industries.
But there’s more to it. For teams using Jira or spreadsheets or similar, answering these questions can take time and effort away from development. It can burden productivity and invites human error.
Is there a better way?
Watch this webinar to learn about:
-Growing challenges of product development teams.
-Ways to manage change, improve visibility throughout the lifecycle.
-How traceability is becoming the linchpin for modern design teams.
-Cost-effective tools to help simplify the complexity.
Prezentacja z ósmego spotkania z cyklu Quality Meetup.
Autor: Michał Stryjak (QA Manager, PiLab SA)
Przez wiele lat ludzie starali się wskazać niezawodne podejście do testowania. Nasz Gość uczestniczył w wielu dyskusjach dotyczących wyższości jednej metody nad drugą, które zwykle sprowadzały się do poszukiwania odpowiedzi na pytanie, czy jakaś konkretna praktyka zmieni świat testów na zawsze.
Już wiele lat temu Cem Kaner zauważył, że najlepsze praktyki głoszone przez jego kolegów wykładowców nie zawsze sprawdzają się dobrze w rzeczywistości. Często obserwował jak procesy i narzędzia stosowane z powodzeniem, np. w startupach, nie sprawdzają się w bankach lub branży medycznej (i vice versa). Z biegiem lat Cem doszedł do wniosku, że coraz więcej osób ma podobne spostrzeżenia dotyczące najlepszych praktyk. Ludzie podzielający jego poglądy (najbardziej znani to James Bach i Bret Pettichord) twierdzą, że aby móc testować dobrze, najpierw trzeba uwzględnić i przeanalizować kontekst. Ich idee znalazły odwzorowanie w siedmiu zasadach, które dzisiaj stanowią podstawę podejścia Context-Driven Testing (CDT). Na spotkaniu Michał opowie nam o podstawach CDT oraz podzieli się pomysłami, jak można wdrażać wspomniane siedem zasad w życie.
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
importance of resources allocation in formal method of software engineering ...abdulrafaychaudhry
Project management is a very wide area of work, particularly in business. It covers many different topics which can be broken into even smaller particles. Work of a project manager is not only about giving people orders and telling them what to do. Many people limit their work of a project manager to supervising their employees and making sure everyone meets their deadline. But a good project manager knows it’s more than that.
Resource allocation in project management is one of those particles which make work of a good PM effective and significant. And even though it may seem simple, it is actually crucial in delivering a great project.
Resource allocation in project management is concerned with creating a plan which can help achieve future goals. There are many resources which have to be allocated when managing a project, beginning from budget to equipment and tools, to data and the project’s plan.
How To Allocate Resources
Resource allocation in project management is so important because it gives a clear picture on the amount of work that has to be done. It also helps to schedule ahead and have an insight into the team’s progress, including allocating the right amount of time to everyone on the team.
Resource allocation allows to plan and prepare for the project’s implementation or achieving goals. It is also possible to analyze existing threats and risks to the project.
But above all, resource allocation in project management helps to control all the workload. This, as a result, contributes to team’s effectiveness at work and what follows later is a satisfying and exhaustive project.
How To Handle Exploding Complexity in Product DevelopmentPerforce
Was everything tested before the product shipped?
Were all requirements met?
Are you sure?
As product development explodes with complexity (and as requirements & tests evolve during development), many design teams struggle to answer these questions with confidence.
Knowledge gaps in product development add risk. Never good—especially in regulated industries.
But there’s more to it. For teams using Jira or spreadsheets or similar, answering these questions can take time and effort away from development. It can burden productivity and invites human error.
Is there a better way?
Watch this webinar to learn about:
-Growing challenges of product development teams.
-Ways to manage change, improve visibility throughout the lifecycle.
-How traceability is becoming the linchpin for modern design teams.
-Cost-effective tools to help simplify the complexity.
Prezentacja z ósmego spotkania z cyklu Quality Meetup.
Autor: Michał Stryjak (QA Manager, PiLab SA)
Przez wiele lat ludzie starali się wskazać niezawodne podejście do testowania. Nasz Gość uczestniczył w wielu dyskusjach dotyczących wyższości jednej metody nad drugą, które zwykle sprowadzały się do poszukiwania odpowiedzi na pytanie, czy jakaś konkretna praktyka zmieni świat testów na zawsze.
Już wiele lat temu Cem Kaner zauważył, że najlepsze praktyki głoszone przez jego kolegów wykładowców nie zawsze sprawdzają się dobrze w rzeczywistości. Często obserwował jak procesy i narzędzia stosowane z powodzeniem, np. w startupach, nie sprawdzają się w bankach lub branży medycznej (i vice versa). Z biegiem lat Cem doszedł do wniosku, że coraz więcej osób ma podobne spostrzeżenia dotyczące najlepszych praktyk. Ludzie podzielający jego poglądy (najbardziej znani to James Bach i Bret Pettichord) twierdzą, że aby móc testować dobrze, najpierw trzeba uwzględnić i przeanalizować kontekst. Ich idee znalazły odwzorowanie w siedmiu zasadach, które dzisiaj stanowią podstawę podejścia Context-Driven Testing (CDT). Na spotkaniu Michał opowie nam o podstawach CDT oraz podzieli się pomysłami, jak można wdrażać wspomniane siedem zasad w życie.
After an introduction to the basic tenets of Agile and some Agile practices, this presentation to Richmond SPIN (Software Process Improvement Network) talks about ways to convince your organization or clients to use Agile software development practices. Based on a presentation given at Agile 2009 by Arin Sime, Senior Consultant with OpenSource Connections.
importance of resources allocation in formal method of software engineering ...abdulrafaychaudhry
Project management is a very wide area of work, particularly in business. It covers many different topics which can be broken into even smaller particles. Work of a project manager is not only about giving people orders and telling them what to do. Many people limit their work of a project manager to supervising their employees and making sure everyone meets their deadline. But a good project manager knows it’s more than that.
Resource allocation in project management is one of those particles which make work of a good PM effective and significant. And even though it may seem simple, it is actually crucial in delivering a great project.
Resource allocation in project management is concerned with creating a plan which can help achieve future goals. There are many resources which have to be allocated when managing a project, beginning from budget to equipment and tools, to data and the project’s plan.
How To Allocate Resources
Resource allocation in project management is so important because it gives a clear picture on the amount of work that has to be done. It also helps to schedule ahead and have an insight into the team’s progress, including allocating the right amount of time to everyone on the team.
Resource allocation allows to plan and prepare for the project’s implementation or achieving goals. It is also possible to analyze existing threats and risks to the project.
But above all, resource allocation in project management helps to control all the workload. This, as a result, contributes to team’s effectiveness at work and what follows later is a satisfying and exhaustive project.
Lean UX - Applying Lean Principles to improve
User Experience in Agile environment. It accomplishes this by getting out of the deliverables business and instead focusing on successful experiences.
The move to Windows 7 can be overwhelming. What starts out as a simple OS migration can quickly snowball into an avalanche of sub-projects and interdependencies that bury you in stress and confusion. With proper planning and careful execution, however, you can navigate your Windows 7 migration with minimal pain, and come out of it with an IT infrastructure that is poised for the next generation of streamlined desktop management. View Eden’s “10 Ways To Stay On Track With Your Windows 7 Migration” to be sure that you’re headed in the right direction.
Why software will never be the same... Discuss why agile and lean development methodologies alone are not enough to compete in today's software startup market. Explore real-time prototyping and minimal viable experiments that can accelerate learning down to hours, not sprints.
Deliverable 2 - Using Visuals to Enhance Viewer PerceptionCompet.docxtheodorelove43763
Deliverable 2 - Using Visuals to Enhance Viewer Perception
Competency
Analyze and interpret perceptual elements of visual media communication to identify effective visual messages.
Scenario
You have been hired by a large law enforcement agency to analyze the images used on advertising billboards in both urban and suburban regions. The billboards visually display a new campaign message to improve neighborhood safety.
During your analysis, you find that the images used on billboards in the urban areas are exactly the same as the images used in the suburban areas. Both images show parents happily talking with law enforcement officers while children run over green lawns having a fun balloon fight. You decide that these images are not sending proper perceptual messages. You decide to create a visual analysis video for the law enforcement agency to share with the administration
For the video visual analysis, you realize you will need to find two new images that are quite different from one another. One image will be used on the urban billboard, and the other image will be used on the suburban billboard. In your video presentation, you will compare and contrast how each image utilizes the following:
1. Compare and contrast the visual elements of cultural familiarity. Explain why it is important to use culturally familiar visuals that are quite different in the urban and suburban billboard images. Include specific visuals in your visual analysis.
2. Identify specific visual examples of the following cognitive elements: memories, experiences, and expectation. Compare and contrast how urban and suburban viewers may be affected differently by those specific cognitive visual elements.
3. Explain the difference between urban and suburban viewers' emotionally engagement with each of the billboard images.
4. Identify visual semiotic codes in both images: metonymic, analogical, displaced, and condensed. Discuss the importance of using these codes. Include specific visuals in each part of your visual analysis.
As you outline your ideas for the video, you decide to record your verbal analysis while analyzing the two visuals in less than seven minutes for added clarity.
/
FEATURE
8 common project management mistakes — and how to avoid them
IT executives and certified project management professionals reveal the most common reasons projects get derailed and
what project managers can do to keep them on track.
By Jennifer Lonoff Schiff
CIO |
JUN 28, 2017 3:00 AM PDT
So many projects, so much mismanagement. That's the refrain of many IT executives. Indeed, even with project
management software, IT projects often wind up taking longer (much longer) than planned and costing more than
budgeted.
While no two projects are exactly the same, the issues that can affect — and potentially jeopardize — them are
often quite similar. And even good project managers can make mistakes when wrangling a big, complex project —
or when being bombarded with change requests..
Deliverable 2 - Using Visuals to Enhance Viewer PerceptionCompet.docxcargillfilberto
Deliverable 2 - Using Visuals to Enhance Viewer Perception
Competency
Analyze and interpret perceptual elements of visual media communication to identify effective visual messages.
Scenario
You have been hired by a large law enforcement agency to analyze the images used on advertising billboards in both urban and suburban regions. The billboards visually display a new campaign message to improve neighborhood safety.
During your analysis, you find that the images used on billboards in the urban areas are exactly the same as the images used in the suburban areas. Both images show parents happily talking with law enforcement officers while children run over green lawns having a fun balloon fight. You decide that these images are not sending proper perceptual messages. You decide to create a visual analysis video for the law enforcement agency to share with the administration
For the video visual analysis, you realize you will need to find two new images that are quite different from one another. One image will be used on the urban billboard, and the other image will be used on the suburban billboard. In your video presentation, you will compare and contrast how each image utilizes the following:
1. Compare and contrast the visual elements of cultural familiarity. Explain why it is important to use culturally familiar visuals that are quite different in the urban and suburban billboard images. Include specific visuals in your visual analysis.
2. Identify specific visual examples of the following cognitive elements: memories, experiences, and expectation. Compare and contrast how urban and suburban viewers may be affected differently by those specific cognitive visual elements.
3. Explain the difference between urban and suburban viewers' emotionally engagement with each of the billboard images.
4. Identify visual semiotic codes in both images: metonymic, analogical, displaced, and condensed. Discuss the importance of using these codes. Include specific visuals in each part of your visual analysis.
As you outline your ideas for the video, you decide to record your verbal analysis while analyzing the two visuals in less than seven minutes for added clarity.
/
FEATURE
8 common project management mistakes — and how to avoid them
IT executives and certified project management professionals reveal the most common reasons projects get derailed and
what project managers can do to keep them on track.
By Jennifer Lonoff Schiff
CIO |
JUN 28, 2017 3:00 AM PDT
So many projects, so much mismanagement. That's the refrain of many IT executives. Indeed, even with project
management software, IT projects often wind up taking longer (much longer) than planned and costing more than
budgeted.
While no two projects are exactly the same, the issues that can affect — and potentially jeopardize — them are
often quite similar. And even good project managers can make mistakes when wrangling a big, complex project —
or when being bombarded with change requests..
Forget the A to Z of why it projects fail, here’s the S to L of successful!Stoneseed Ltd
THE TOP TEN WAYS TO KEEP YOUR PROJECT ON TRACK
CREATED BY: DAVID COTGREAVE
A number of articles have either dropped in my Office 365 inbox this week, or on various social media feeds, each of them detailing a list of the reasons why IT Projects fail.
That's a rather negative way to approach it.
The best sports teams didn't build success by checking out why other teams were losing - they focussed on winning. You should too.
You can certainly learn from the mistakes of others (and yourself) but instead of dwelling on the A to Z of failures, how about championing the S to L of what happens when IT projects are SUCCESSFUL.
S - is for Skills
U - is for Understanding
C - is for Communication (and clarity)
C - is for Change Leadership
E - is for Efficient Execution
S - is for Systems
S - is for Supervision
F - is for Fact-Rooted analysis
U - is for User input
L - is for Learn
The S to L of SUCCESSFUL.
If it sounds simple, it's because it is. Sort of.
Except, of course, for the fact that behind each of the ten points above there lies a lot of hard work and hard earned experience - sometimes it's like herding cats - but the gains are there to be won.
Just don't start with a list of why projects fail.
Further details of how Project Management as a Service can help, can be found on our website www.stoneseed.co.uk
Project Management vs Task Management: What Works Best for YouOrangescrum
Task management works better for simplistic activities be it solo or with a team. Project management on the other hand takes a little more in terms of planning and execution. Orangescrum project and task collaboration tool helps you run large complex projects as well as your to-do lists all at once in a highly collaborative environment.
Similar to Software development project management (20)
Into the Box Keynote Day 2: Unveiling amazing updates and announcements for modern CFML developers! Get ready for exciting releases and updates on Ortus tools and products. Stay tuned for cutting-edge innovations designed to boost your productivity.
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I ...Juraj Vysvader
In 2015, I used to write extensions for Joomla, WordPress, phpBB3, etc and I didn't get rich from it but it did have 63K downloads (powered possible tens of thousands of websites).
Paketo Buildpacks : la meilleure façon de construire des images OCI? DevopsDa...Anthony Dahanne
Les Buildpacks existent depuis plus de 10 ans ! D’abord, ils étaient utilisés pour détecter et construire une application avant de la déployer sur certains PaaS. Ensuite, nous avons pu créer des images Docker (OCI) avec leur dernière génération, les Cloud Native Buildpacks (CNCF en incubation). Sont-ils une bonne alternative au Dockerfile ? Que sont les buildpacks Paketo ? Quelles communautés les soutiennent et comment ?
Venez le découvrir lors de cette session ignite
We describe the deployment and use of Globus Compute for remote computation. This content is aimed at researchers who wish to compute on remote resources using a unified programming interface, as well as system administrators who will deploy and operate Globus Compute services on their research computing infrastructure.
top nidhi software solution freedownloadvrstrong314
This presentation emphasizes the importance of data security and legal compliance for Nidhi companies in India. It highlights how online Nidhi software solutions, like Vector Nidhi Software, offer advanced features tailored to these needs. Key aspects include encryption, access controls, and audit trails to ensure data security. The software complies with regulatory guidelines from the MCA and RBI and adheres to Nidhi Rules, 2014. With customizable, user-friendly interfaces and real-time features, these Nidhi software solutions enhance efficiency, support growth, and provide exceptional member services. The presentation concludes with contact information for further inquiries.
A Comprehensive Look at Generative AI in Retail App Testing.pdfkalichargn70th171
Traditional software testing methods are being challenged in retail, where customer expectations and technological advancements continually shape the landscape. Enter generative AI—a transformative subset of artificial intelligence technologies poised to revolutionize software testing.
Field Employee Tracking System| MiTrack App| Best Employee Tracking Solution|...informapgpstrackings
Keep tabs on your field staff effortlessly with Informap Technology Centre LLC. Real-time tracking, task assignment, and smart features for efficient management. Request a live demo today!
For more details, visit us : https://informapuae.com/field-staff-tracking/
In software engineering, the right architecture is essential for robust, scalable platforms. Wix has undergone a pivotal shift from event sourcing to a CRUD-based model for its microservices. This talk will chart the course of this pivotal journey.
Event sourcing, which records state changes as immutable events, provided robust auditing and "time travel" debugging for Wix Stores' microservices. Despite its benefits, the complexity it introduced in state management slowed development. Wix responded by adopting a simpler, unified CRUD model. This talk will explore the challenges of event sourcing and the advantages of Wix's new "CRUD on steroids" approach, which streamlines API integration and domain event management while preserving data integrity and system resilience.
Participants will gain valuable insights into Wix's strategies for ensuring atomicity in database updates and event production, as well as caching, materialization, and performance optimization techniques within a distributed system.
Join us to discover how Wix has mastered the art of balancing simplicity and extensibility, and learn how the re-adoption of the modest CRUD has turbocharged their development velocity, resilience, and scalability in a high-growth environment.
Navigating the Metaverse: A Journey into Virtual Evolution"Donna Lenk
Join us for an exploration of the Metaverse's evolution, where innovation meets imagination. Discover new dimensions of virtual events, engage with thought-provoking discussions, and witness the transformative power of digital realms."
AI Pilot Review: The World’s First Virtual Assistant Marketing SuiteGoogle
AI Pilot Review: The World’s First Virtual Assistant Marketing Suite
👉👉 Click Here To Get More Info 👇👇
https://sumonreview.com/ai-pilot-review/
AI Pilot Review: Key Features
✅Deploy AI expert bots in Any Niche With Just A Click
✅With one keyword, generate complete funnels, websites, landing pages, and more.
✅More than 85 AI features are included in the AI pilot.
✅No setup or configuration; use your voice (like Siri) to do whatever you want.
✅You Can Use AI Pilot To Create your version of AI Pilot And Charge People For It…
✅ZERO Manual Work With AI Pilot. Never write, Design, Or Code Again.
✅ZERO Limits On Features Or Usages
✅Use Our AI-powered Traffic To Get Hundreds Of Customers
✅No Complicated Setup: Get Up And Running In 2 Minutes
✅99.99% Up-Time Guaranteed
✅30 Days Money-Back Guarantee
✅ZERO Upfront Cost
See My Other Reviews Article:
(1) TubeTrivia AI Review: https://sumonreview.com/tubetrivia-ai-review
(2) SocioWave Review: https://sumonreview.com/sociowave-review
(3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review
(4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
How to Position Your Globus Data Portal for Success Ten Good PracticesGlobus
Science gateways allow science and engineering communities to access shared data, software, computing services, and instruments. Science gateways have gained a lot of traction in the last twenty years, as evidenced by projects such as the Science Gateways Community Institute (SGCI) and the Center of Excellence on Science Gateways (SGX3) in the US, The Australian Research Data Commons (ARDC) and its platforms in Australia, and the projects around Virtual Research Environments in Europe. A few mature frameworks have evolved with their different strengths and foci and have been taken up by a larger community such as the Globus Data Portal, Hubzero, Tapis, and Galaxy. However, even when gateways are built on successful frameworks, they continue to face the challenges of ongoing maintenance costs and how to meet the ever-expanding needs of the community they serve with enhanced features. It is not uncommon that gateways with compelling use cases are nonetheless unable to get past the prototype phase and become a full production service, or if they do, they don't survive more than a couple of years. While there is no guaranteed pathway to success, it seems likely that for any gateway there is a need for a strong community and/or solid funding streams to create and sustain its success. With over twenty years of examples to draw from, this presentation goes into detail for ten factors common to successful and enduring gateways that effectively serve as best practices for any new or developing gateway.
Enterprise Resource Planning System includes various modules that reduce any business's workload. Additionally, it organizes the workflows, which drives towards enhancing productivity. Here are a detailed explanation of the ERP modules. Going through the points will help you understand how the software is changing the work dynamics.
To know more details here: https://blogs.nyggs.com/nyggs/enterprise-resource-planning-erp-system-modules/
1. Miss any of these 10 important points in a
software development project and you are most
likely going to fail!
Medullus Systems
Excellence in software development, Cloud, EDI, Reporting, ERP, Sharepoint, Legacy software, Project Management &
Consulting…for your business
2. Who should read this: Anyone remotely connected with IT!
Tips: Be sure to click through the links - there are some cool videos and tools we use that you might find helpful.
3. (1) Start an official charter meeting - even
if it is a 1 day project, and list everyone
involved in the project
It just makes the project official. Create a
document, project asset, minutes or it can
even be an email to all involved stating (a)
project name, (b) project manager, (c) team
and responsibilities (could have a RACI if it is
a more involved project), (d) briefly, what the
project is going to achieve
4. 2) Create a scope baseline, get it signed by the project champion
and make it visible to every stakeholder
We call it “spec freeze”. Scope, simply put, is the sum total of what
the project needs and agreed upon by all parties. The reality is that
the scope is forever changing. James in Accounting thought of
something new, Mark in procurement had a better idea, Jill in
Inventory thought of one exception…you get the picture. We create
detailed wireframes upfront - it can be time consuming, but it is totally
worth it. EVERY TIME. It gets the project “live” in front of the end user
before we even start to develop. So once James, Mark, Jill and the
gang is sure (at least as of now!) we stamp it as a “scope baseline”.
Any change is recorded but it is kept in a queue till after we deliver on
that initial scope baseline. For the customer they see an end and not
an unending project with changes upon changes. It keeps our
development, testing and implementation clean.
5. (3) Research and find out all the negative
stakeholders (not just the positive ones)
Every project has at least 1 negative stakeholder,
someone who is negatively affected by the
outcome of the project. It could be a person, a
department, a customer, a vendor, a belief or
even a competitor. Sometimes such impacts
cannot be avoided. But it is a good idea to know
how to work through them. Surprises are never
pleasant during a software development project.
6. (4) Create 2 specs - one for the techies and one for the
business folks and make sure they are both synced with
the scope
In any software development project you will have to find out
who the main consumer of the software will be - it can be 1 or
more users. That user or users will be able to articulate what the
project needs to do. As a software architect and also as a
project manager you should be able to see the software from
the eyes of the business as well as the eyes of IT. If you cannot
do this, then make sure you have someone who can do that or
tag team. When you are creating the specifications, create a
user spec and a software spec - make sure these are in sync.
Updates to one should update the other and communicated to
the right parties.
7. (5) Regardless of your project management methodology
(waterfall, scrum etc), make sure you have a detailed
work breakdown structure
Take a project. Break it down into modules - a module is a
finite part that can be developed and tested independent from
the rest. Now take each module and break it into tasks. A task
is a finite part of a module that can be measured start to finish
- one to which you can clearly add a start and an end date.
Next take the task and break it (if you can) into chunks that
makes it easy to estimate time. There are many ways to
estimate time - but increments of 2, 4, 6 or 8 hrs works for us.
So 5 hrs is 6; 3 hrs is 4 (round up). We also use PERT
methods if there are several unknowns in the beginning.
8. (6) Write out the test plans in a bug
management system - it could even be google
docs or excel - but write it
When you articulate and write down a test plan
your testing becomes more methodical. The
project can be just 1 text box and 1 button. But
when you start to write it out in steps 1, 2, 3 etc
you will see a 4th test that you would have
probably missed. You may use automated testing
tools, but for functional testing this is a must.
9. (7) Track progress daily - project the finish line
based on current completion
Especially true for those long projects, spread across
multiple teams, time zones and sub projects (more like a
program). A daily top down view of the project
milestones, KPIs like burndown charts or % completion
or earned value measures should be assessed daily -
you can do it start or end of the day. Surprises spring
when a project is “sleeping” or on “auto-pilot” - those are
not good words for a software development project. It
needs to be tracked, monitored and managed. DAILY.
10. (8) Keep communication channels open across all
team members
Getting mathematical! Number of channels = n*(n-1) - so if
5 people are involved, that creates 5*4 = 20 channels - that
is a lot of communication! The single most reason why
projects fail is lack of clear communication and open
channels. Daily 15 minute meetings (scrums) is one good
solution. It should be unofficial - answer 3 questions - what
did you do yesterday, what will you do today and what
roadblocks are you facing to get the project done. Have
each of the 5 people (or whatever the project team size)
answer these. Another option is to use a collaboration tool
like Basecamp, Producteev, Asana, Sharepoint, Zoho etc.
11. (9) Be honest - dead honest
If you messed up own up to it right then and there with an apology,
but more importantly, with a way to fix it and how it will impact the
work breakdown structure and the timeline. It lets the project
manager recalculate, crash the project or rearrange resources etc.
If something is sensitive, but you feel it will affect the success of the
project be honest and mention it, but mention it to the right person.
First explain why you are going to talk about it and then explain
how the situation will affect the project.
Politics is a great way to get things done! But politicking for the
sake of it or to hide inefficiencies is a cancer to any project. Be
honest and call it out if you see it. Create the “political arena” where
it can be brought out to the key stakeholders.
12. (10) Always close the project, finished
or not, successful or not
Let the project champion know “this closes
the project.” Then write 1 (just 1) main
lesson learned from the project. This really
helps. At a glance you can see how many
projects you have done (count the lessons
learned!) and before starting a new project
it is a good read.
13. Have a good time with everyone, enjoy
the ride and remember:
“The goal of a software project is to
solve a business problem. It is
empowering when you know that your
software will help a business to
prosper.”